I am facing an issue where my Exchange 2013 server has run into trouble mounting databases. Also the Microsoft Exchange Replication has crashing repeatedly.
Attempting to mount database result in error during the crash events.
Error: An Active Manager operation failed.
Error: The database action failed.
Error: The Microsoft Exchange Replication service may not be running on server
It becomes a race condition to mount the database during the very brief window between the service restarting and then crashing
Restarting the “Microsoft Exchange Replication” Service – crashes with Event ID 7031 – The Microsoft Exchange Replication service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Restarting the “Microsoft Exchange Mailbox Replication” Service
Restarting the “Microsoft Exchange Mailbox Transport Delivery & Submission” Services
Restarting the host server of Exchange Server 2013
I’ve check that the Exchange Server has proper communication to the domain controllers.
I’ve check that the logon server for the Exchange Server was also in good health.
The only new introduction to our Exchange environment has been the CU6 update released on August 26, 2014. Source: http://support.microsoft.com/kb/2961810
We recently rebooted our Exchange for maintenance and these issues started.
I hope to be able to provide more info on this as I search for a solution.
Office 365 Support are no help and directed me to work with the Product Support Team. Product Support indicates known bugs in my situation, although they have not been made public and wouldn’t go into further details.
What they now want me to turn up a new Exchange 2013 Server. Download and install CU6 (again) and install it on the new server.
Once installed and working they want me to perform a “Forklift” migration, of my databases.
Update: 2014-09-29 – Problem Fixed
So it turns out, that the cause of my issue came from an application event log in the following location which contain corrupted items: Applications and Services Logs / Microsoft / Exchange / MailboxDatabaseFailureItems / Operational
Once removed I was able to restart the service and all was working as normal. Command issued: Wevtutil.exe cl “Microsoft-Exchange-MailboxDatabaseFailureItems/Operational”
12 replies on “Exchange 2013 DB’s not mounting, Exchange Replication crashing”
I’m facing the exact same issue. I’ve got an 8 node dag and on one of my servers after installing cu6 and rebooting the replication service will not stay runnning. Just starts and stops constantly with the same error in the event logs as yours. I cant find any help with this issue but I’m not about to rebuild this server. Blows my mind that that is what they had you do. Guess I’ll open a support case.
Just got off phone with MS. Its a bug with CU6, all you have to do is clear the operational logs under MailboxDatabaseFailureItems using this command:
Wevtutil.exe cl “Microsoft-Exchange-MailboxDatabaseFailureItems/Operational”
AFter that the service stays running. No rebuild necessary.
Thank You Richard for the feedback. I was able to get Microsoft to help after hours and days of steps.
They had admitted to me the issue was with CU6 and that I should download CU6 again if I intend to install on other systems.
I take it they fixed it in other packages. I guess now I need to run a MD5 sum on the original download to compare to know for sure.
They probably didn’t know the fix at the time you called them. They just knew that reinstalling cu 6 fixes the issue. Having you reinstall cu6 would have cleared those operational logs, which were the culprit.
Indeed it would have. Over the years I have noticed a decline in quality in the CU, SP, and updates in general.
Most of all the support staff are excellent in “trying to” assist, but fall short of technical knowledge of the product.
just wanted to say thanks on this article. I literally spent all day looking for a resolve on my replication service failing over and over on one of my mailbox servers. I to updated my exchange environment to CU6. Just last night actually. After clearing the specified log my replication service stayed running and i am now working on getting my DAG back to operational.
You are welcome and I am glad my posting has helped you resolve this issue.
[…] a previous post I wrote about my Exchange 2013 CU6 adventure and how it caused my Exchange Replication Services to […]
I was getting totally mad with this, and it appears to be ok now!
I have a simple 2013 exch server, this error screwed up everything. your log clear fixed it.
thank you so much
I am glad that all worked out for you. Thank you for following my steps and for the comment. It is truly appreciated – Jermal
Stuff like that makes me wish I went into drywall.