Thursday, 31 December 2015

Content Index State Failed in Exchange 2016

After a failover or similar event, you may find that a passive mailbox database copy has a ContentIndexState of Failed or FailedAndSuspended in your Exchange 2016, 2013 or 2010 Database Availability Group.

In our case, we have four mailbox database copies and one of them, MDB03, has a ContentIndexState of FailedAndSuspended:

Get-MailboxDatabaseCopyStatus | sort Name | ft -AutoSize


To resolve this, we need to use the Update-MailboxDatabaseCopy cmdlet and specify the -CatalogOnly switch so that only the content index is re-seeded rather than the entire database:

Update-MailboxDatabaseCopy MDB03\LITEX01 -CatalogOnly


After this completes, check your content index state:

Get-MailboxDatabaseCopyStatus | sort Name | ft -AutoSize


As we can see, all content indexes are healthy and our issue is resolved.


  1. Same problem with Exchange 2016 but cannot update the content index state with below error:
    Seeding of content index catalog for database 'EXDB02' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There was no endpoint listening at net.tcp://localhost:3863/Management/SeedingAgent-2BE8A1F1-3986-4A07-BD39-61F6621EFDAC12/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
    Any idea...?

    1. I am getting same message. did you find any solution?