Scenario: Exchange 2013 multiple databases. Replication service starts and stops constantly after reboot.

After a reboot to a non-response Exchange 2013 Server, when running the Get-MailboxDatabaseCopyStatus command was run, all DB’s showed with a Service Down status, after a few seconds, the status changed to initializing and then back to Service Down.


The following events were logged:

Event ID 106 and 4138. It was reporting about 1 database that couldn’t mount.


Next, Navigate to Applications and Services Logs -> Microsoft -> Exchange -> MailboxDatabaseFailureItems -> Operational.

Here it will give you the name of the DB that cannot replay logs. The next step is to suspend that database.

You can do so by running the following command:

  • Suspend-MailboxDatabaseCopy -Identity “DBName”

After a few seconds, all the databases should mount and that one will show as “failed and suspended”.

You can now update the database copy, in this case it was easier to use the -DeleteExistingFiles switch:

  • Update-MailboxDatabaseCopy -Identity “DBName” -DeleteExistingFiles

Depending on the DB size this can take a while but all should be healthy after this.

Hope it helps.

By edward

4 thought on “Exchange 2013 – Microsoft Exchange Replication Service restarting”
  1. Thanks, this helped with my Exchange 2016 after updates (KB4036108 – Security update for Exchange 2016 CU5), KB3192137, and KB4038782 – Both Windows updates) were installed and the server rebooted. The other server in the DAG had the same updates and reboot and was fine.

Comments are closed.