Repairing a Failed Content Index in Exchange Server 2013 & 2016

Sometimes you can hear users complain about not being able to search in Outlook and OWA, one thing that often causes this, is the Content Indexing in Exchange server.

So how to find out?

Go to Exchange Powershell, and type:

Get-MailboxDatabaseCopyStatus * | sort name | Select name,status,contentindexstate

You will get a status of your databases ContentIndexState that will show:

Catalog state: FailedAndSuspended.

Stop theese services:

StopService MSExchangeFastSearch

StopService HostControllerService

After that, find out where the Exchange database involved, resides:

GetMailboxDatabase <DATABASE NAME> | select EdbFilePath

In here, we find the GUID folder for the index, delete that folder or rename it:

Start the two services again:

StartService MSExchangeFastSearch

StartService HostControllerService

Now the indexing service will be starting up again, slowly crawling through the database, but please remember, this will take a long time to complete, also if the database is big!

Everything can be done during work hours, without any kind of interruption.

After a while, try to run this command again:

As you can see, now it’s not suspended anymore, just “Failed”

Then after some time, run the command another time:

 

An now we are crawling 🙂

Finally we will reach this:

And search should start working again 🙂

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close