Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, December 1, 2011 10:24 AM
Hello,
I'm unable to activate a database copy.
It seems everything is OK with the copy (identical size, same log files etc) but when attempting a failover we get messages like the one below
This is the case both for existing database (where failover worked before without any problem) and new fresh created.
One of the servers in the DAG was recently removed an re-inserted in the domain without being removed from the DAG
Could this has something to do with this cryptic error
Any help appreciated
Daniel
Details:
Move-ActiveMailboxDatabase
Failed
Error:
An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: Error 0x6d1 (The procedure number is out of range) from cli_AmMountDatabaseDirect3 [Database: ETROTEST4, Server: ETROEXBASE1.etro.vub.ac.be]
An Active Manager operation failed. Error: Operation failed with message: Error 0x6d1 (The procedure number is out of range) from cli_AmMountDatabaseDirect3
Error 0x6d1 (The procedure number is out of range) from cli_AmMountDatabaseDirect3
Exchange Management Shell command attempted: Move-ActiveMailboxDatabase -Identity 'ETROTEST4' -ActivateOnServer 'ETROEXBASE2' -MountDialOverride 'None'
Daniel
All replies (7)
Sunday, December 4, 2011 6:06 AM âś…Answered
Hi Daniel,
Base on my research,
Version 14.1 (Build 218.15) = Microsoft Exchange Server 2010 SP1 (No rollup).
Version 14.0 (Build 639.21) = Microsoft Exchange Server 2010 RTM (No rollup).
My suggestion is that contact Microsoft support.
There is a version control problem in the application that can only be fixed by the application supplier (procedures were added to an .IDL file without changing the version number).
Rowen
TechNet Community Support
Thursday, December 1, 2011 11:36 AM
hi,
please check this post;
regards,
Mumin CICEK | www.cozumpark.com | Please click Vote As Helpful if it is helpful for you and Propose as Answer!!!
Thursday, December 1, 2011 1:36 PM
Hi,
I tried this
Databases are healthy but
[PS] C:\Windows\system32>Update-MailboxDatabaseCopy -Identity ETRO_DELETE\ETROEXBASE2 -CatalogOnly
A server-side seed operation has failed. Error: Content indexing operation failed with the following message: The seeding operation encountered an error while trying to contact the search service. Error: Microsoft Exchange Search Service may not be running on server ETROEXBASE1. Specific RPC error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_PauseIndexing [Database: ETRO_DELETE, Server: ETROEXBASE2.etro.vub.ac.be] + CategoryInfo : InvalidOperation: (:) [Update-MailboxDatabaseCopy], CiSeederRpcOperationFailedException + FullyQualifiedErrorId :F013731,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy
Microsoft Exchange search is however running
[PS] C:\Windows\system32>Get-Service -Name *search*
Status Name DisplayName
* *
Running MSExchangeSearch Microsoft Exchange Search Indexer
Running MSExchangeTrans... Microsoft Exchange Transport Log Se...
Daniel
Friday, December 2, 2011 2:30 AM
Hi Daniel,
Please help to verify below points:
1) Inconsistent Service Pack version between Node 1 and Node 2
2) Replication latency is high due to network congestion since customer only have one network which use for MAPI and replication connection
Thanks.
Rowen
TechNet Community Support
Friday, December 2, 2011 11:44 AM
Hi,
Both member servers have Win2008R2 with SP1 and all updates till last week
They both have the exchange SP1 and Rollup 5 (and all other updates untill last week)
I tried to reduce the number of client connections but no difference
Whatever I do now...creating a new database copy, seeding, activating... all gives the error to check if Exchange search is running (yes it is) and "There are no more endpoints available from the endpoint mapper"
I created even a new exchange server, made it part of the DAG and tried database failover to and from that server. No change, same error.
To me it seems like the DAG is bad although replication is working (size of database and number of logs in copy are correct and all cmd-lets give clean bill of health)
Can I remove the DAG and recreate without loosing all the copies (it's a lot of data if it need to be re-copied)
Regards
Daniel
Daniel
Friday, December 2, 2011 11:50 AM
ETROEXBASE3 is the new one (at this moment not part of the DAG). not related to this problem but strange to notice that this server ha a different AdminDisplay although all the updates are applied (up to rollup 5)
[PS] C:\Windows\system32>get-exchangeserver | ft -property identity, ExchangeVersion, Admindisplayversion
Identity ExchangeVersion AdminDisplayVersion
ETROEXBASE1 0.1 (8.0.535.0) Version 14.1 (Build 218.15)
ETROEXHC1 0.1 (8.0.535.0) Version 14.1 (Build 218.15)
ETROEXBASE2 0.1 (8.0.535.0) Version 14.1 (Build 218.15)
ETROEXBASE3 0.1 (8.0.535.0) Version 14.0 (Build 639.21)
Daniel
Wednesday, December 7, 2011 8:44 AM
I do not know why these numbers are what they are.
I have these numbers but WITH SP1 and WITH all rollups
After re-applying SP1 to the new server, I'm now able to replicate again.
This solved the problem but does not explain why the problem started in the first place (as I created this new server because fail-over didn't worked anymore with above mentioned error). Now, after re-applying SP1 on the new server, failover also works again between the old servers.
Anyway, thanks for the support!
Daniel
Daniel