MSExchange Mailbox Replication
MSExchange Mailbox Replication gives the error below in the application log:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '8877f932-3aa3-4369-b39b-2
Database GUID: '419f5625-68be-4d9a-98cc-8
Error: Database 'e43db18a-c9b6-442e-b38e-9
I have search throughout google and not yet found a good solution to the problem.
I have checked for move requests and so on. Only reference is for my nr. 2 database.
Exchange is a 2 node DAG CAS/MB setup exchange 2013 on server 2012 R2
Any good advice 2 this ?
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '8877f932-3aa3-4369-b39b-2
Database GUID: '419f5625-68be-4d9a-98cc-8
Error: Database 'e43db18a-c9b6-442e-b38e-9
I have search throughout google and not yet found a good solution to the problem.
I have checked for move requests and so on. Only reference is for my nr. 2 database.
Exchange is a 2 node DAG CAS/MB setup exchange 2013 on server 2012 R2
Any good advice 2 this ?
ASKER
I am on an On-Prem environment for this setup. No Hybrid yet. All checks where good on both nodes.
State of databases and database copies are fine. All seems to be good but the replication error is flooding my log and i can also see that sometimes the replication service uses alot of ressources. Which is the reason i want to eliminated this error.
State of databases and database copies are fine. All seems to be good but the replication error is flooding my log and i can also see that sometimes the replication service uses alot of ressources. Which is the reason i want to eliminated this error.
Oh ok. Did you run Get-MailboxDatabase "Database GUID" | ft name, server to see which DB is causing the issue.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also have you tested replication on your DAG nodes. If not I would suggest testing replication. To test run the following:
Test-ReplicationHealth -Identity mailboxservername
I had this error before and never got an answer even from Microsoft. If replication is working and failover works correctly, I wouldnt worry about it. I'm in a hybrid envrionment and never got a resolution about this error, but it has never caused any issues.
You can also check that Database GUID by running the following to see which DB had the issue:
Get-MailboxDatabase "Database GUID" | ft name, server
Verify healthy state of all DBs and replication health, and you should be fine.