Fix Exchange Database Content Index State Failed and Suspended Error

Reading Time: 3 minutes

One of the most common Exchange Server problems, “Fix Exchange Database content Index State Failed and suspended error,”. In this blog post, we will tell you how to fix this exchange database error.

Many Organisations are using Exchange Server extensively to manage their day-to-day operations, internal communications, and other daily tasks. Running multiple operations often puts pressure on the server, causing complex failures. 

One of the problems seen by customers accessing Exchange through Outlook Web Access is “Database Content Index Status Failed And Suspended Error.

Manual method to Fix exchange database content index state failed and suspended error:-

To resolve the “Exchange database content index state failed and suspended” error, users have to follow the steps shown below with Exchange Management Shell.

Condition 1: When the Exchange server is a part of a database availability group

1. Run the following command in EMS to see which content indexes are affected and to display the failed or suspended status:

Get-MailboxDatabase Database Name | Get-MailboxDatabaseCopyStatus |Select Name,*index*

2. Use the command listed below to fix the corrupted catalog of the damaged database:

Update-MailboxDatabaseCopy Database\Server1 -sourceserver Server Name – catalogonly

Enter the database name in the Database Server format along with the Source Server Name. Depending on the size of the database, the update will time out.

3. Run the command below and check the status to see if the command was successful in repairing the files:

Get-MailboxDatabase Database Name | Get-MailboxDatabaseCopyStatus | Select Name,*index*

If it shows a healthy status, the error has been resolved, and mailboxes on the Exchange server can be discovered.

Condition 2: When the Exchange server is not a part of a database availability group

Execute the following cmdlets to first stop the Exchange services Microsoft Exchange Search and Microsoft Exchange Search Host Controller that are currently functioning in the background:

1. For the Search Function in Microsoft Exchange:

Stop-Service MSExchangeFastSearch

2. Regarding the Microsoft Exchange Search Host Controller service:

Stop-Service HostControllerService

The Exchange database folder saving location should now be moved to the same system. Please look for the GUID folder containing the long string and delete it along with any associated subfolders containing the content index of the database.

3. Restart the above services by issuing the following short commands respectively:

Start-Service MSExchangeFastSearchStop-Service HostControllerService

4. It will take some time after issuing the command for the new database content index to be created within the new long string folder.

5. Now, use the below command to check the content index status of Exchange database:

Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus | Select Name,*index*

An automated method to Fix exchange database content index state failed and suspended error:-

Using the comprehensive SysInspire Exchange Server Recovery Software, you can fix corrupted EDB files and migrate them to PST and other formats. It has a straightforward user interface and simple navigation which makes it easy to recover from highly corrupted EDB files and recover all the data with its consistency. 

Additionally, the software works with every Exchange Server version including 2019, 2016, 2013, 2010, 2007, 2003, and 2000.


The common error “Content indexing status is failed and suspended” can appear at any time when using Outlook Web Access to access Exchange. Searching the mailbox is necessary to fix the problem, even if it doesn’t damage any data or make Exchange Server inaccessible. We have included two method fixes for the “Content indexing status is failed and suspended” issue in this article. To fix corrupted EDB files, we recommend an automated solution called SysInspire for Exchange Server Recovery.

Leave a Reply