34 C
Thursday, May 23, 2024

Rebuild an Index on Exchange 2013/2016 for Specific Databases

Let see how to rebuild and Content Index on Exchange 2013/2016 if the content index of the primary database went to a bad shape.

Note : This process takes more I/O on your disk . and increases the load on the server. if you have multiple databases on the same disk/server. Consider doing one by one.

If the Content index of the DAG copy failed you can run

Update-MailboxDatabaseCopy  "DBname\Servername" –CatalogOnly

If the Content index of the primary DB failed

Get-MailboxDatabaseCopyStatus -Server EXCH2016A | fl

ExtendedErrorInfo                     :
SuspendComment                        :
RequiredLogsPresent                   :
SinglePageRestore                     : 0
ContentIndexState                     : FailedAndSuspended
ContentIndexErrorMessage              : The content index is corrupted.

ContentIndexErrorCode                 : 19
ContentIndexVersion                   :
ContentIndexCrawlVersion              :
ContentIndexBacklog                   :
ContentIndexRetryQueueSize            :


Stop below Exchange Services –

Microsoft Exchange Search  – MSExchangeFastSearch

Microsoft Exchange Search Host Controller – HostControllerService


Go to the affected database location – Move the Catalog folder to a different location –

Start the above services back.


Content Index will kick off (This process takes time)– going to unknown –> Crawling –> Healthy.



Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Related Articles


  1. Hi Satheshwaran, could you please at my post below and help me with Exchange Search.

    I’m running Exchanging 2013 with two mailbox servers in a DAG. Get-MailboxDatabaseCopyStatus * showed both servers in FailedAndSuspended state. I think this issue occurred after I extended disk space on the mailbox servers. I tried Update-MailboxDatabaseCopy -CatalogOnly but that didn’t help I presume as there was no Heatlty copy present.

    On the passive node I stopped Exchange Search and Exchange Host Controller service, renamed .single to .single.old and started the service again which created a new folder. But state was still showing FailedAndSuspended, so I tried to do same on the Active node and upon service start status was changed to Crawling on active node and passive was still showing FailedAndSuspended.

    It took more than 24 hours and status was changed from Crawling to Failed on Active node. Then again on the passive node I stopped and started Exchange Search and Exchange Host Controller service, after a while status was changed from Failed to Crawling and then to Healthy. Once status was healthy then I ran MailboxDatabaseCopy -CatalogOnly which made the active node healthy as well.

    Now the issue which I’m facing is that search still isn’t working other than recent emails (1 day old emails)

    .single.old size is showing as 30 GB while new folder .single is showing only 6 GB. Is there any possible solution I could fix the search issue?

    Could you please help me to resolve this.




Please enter your comment!
Please enter your name here

× How can I help you?