How to Resolve Content Index State Suspended Exchange 2016

Considering the global acceptance of Microsoft Exchange Server as a reliable mail and communication service, a significant increase in the number of its users is evident. This increases the volume of mailbox data and hence the database that contains all the information. This data overload keeps the database vulnerable to several errors and one of them is the issue of ‘content index state suspended’. 

A common issue in Exchange 2016 and other versions, it does not hamper the email exchange, but can cause problems in search activities. A user wanting to connect to the Outlook Web Application (OWA) to search in a particular mailbox is more likely to get this error.

If you have a Database Availability Group (DAG) setup, the error message content index state suspended in Exchange 2016 can create hassles when trying to switch over to a different server. This obstruction may not be significant to the users but it could still affect your server, leaving the mailboxes inaccessible to the users. 

Reasons behind Content Index State Failed and Suspended

This error may crop up due to any of the numerous probable cases arising in Exchange Server 2016.

• Data migration from an older Exchange 2016 version
• Issues related to storage space
• A bad, incompatible, or improper installation of the latest Cumulative Update (CU)
• Database disk runs out of space, causing the server to face index failure or suspend error
• Antivirus software, installed or configured wrongly, locking the Exchange 2016 server files
• Improper working of the replication in a Database Availability Group (DAG)

To identify the issue regarding the inability to search in their mailboxes, you can use the PowerShell cmdlet MailboxDatabaseCopyStatus

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

This will display the database status and the state of the content index. If you encounter a FailedAndSuspended message, proceed to resolve this issue as soon as possible. 

Resolve the issue in a Single Exchange Server

This case involves a standalone Exchange server with a failed or suspended content index state. It is not a part of any Data Availability Group. You can rebuild the database back to working condition by using the following steps:

1. Stop Microsoft Exchange Services

Stop the Services – Microsoft Exchange Search & Microsoft Exchange Search Host Controller by using the Stop-Service cmdlet:

Stop-Service MSExchangeFastSearch

Stop-Service HostControllerService

Alternatively, do the following on your system:

• Press Windows+R 
• Write services.msc in the Run dialogue box and click OK.
• Find Microsoft Exchange Search, right-click the service, and click Stop
• Find & Microsoft Exchange Search Host Controller, right-click the service and click Stop

2. Delete the content index

Delete the content index from the database path as mentioned below:

• Open File Explorer
• Navigate to the location where you have stored the EDB file of the database that flashes the error
• Delete the folder with GUID 

In case you do not know the file path, use the Get-MailboxDatabase PowerShell cmdlet to know the location of the database

Get-MailboxDatabase <database name> | select EdbFilePath

3. Restart the services

• Use services.msc to open the Services page
• Restart the Microsoft Exchange Search & Microsoft Exchange Search Host Controller Services page  

 Alternatively, use the below PowerShell cmdlet: 

Start-Service MSExchangeFastSearch 

Start-Service HostControllerService

This will enable the services to start indexing and crawling the database content. 

After the process completion, use the Get-MailboxDatabaseCopyStatus cmdlet again. You will find your database in a healthy state.

Resolution when Exchange 2016 is a part of the Data Availability Group

If your Exchange is a part of the DAG Setup, multiple database copies may or may not face damage because of a corrupt content index state. To deal with the errors in this case, use the below steps:

1. Analyze the content indexes

Run the following command to analyze and display the content index with suspended or failed status.

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

2. Reseed the content index

Use a healthy copy of the database to reseed it by using the following PowerShell command:

Update-MailboxDatabaseCopy < YourDatabaseName >\<YourServerNam> -CatalogOnly -BeginSeed

This command may be time-consuming. Once it completes, run the Get-MailboxDatabaseCopyStatus cmdlet to get the content index status:

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

A healthy state of the database will indicate successful resolution of the error: Content index state failed or suspended, in Exchange 2016. It will enable you to search the mailboxes like before.

If still you are facing the issue, examine the replication logs for any errors associated with the specific Exchange database. If you continue to experience issues, consider running a database repair using Eseutil. You can also use an Exchange EDB recovery tool. Leveraging Stellar Repair for Exchange is a smart choice in this regard.

Stellar Repair for Exchange

Using this tool can turn out to be an ideal method to bring your database back to a healthy condition. 

Its prominent features are as follows:

• Restores offline or dismounted Exchange EDB files efficiently
• Exports EDB file to Live Exchange Server, PST, or Office 365
• Supports Exchange 2019, 2016, 2013, and all the other previous Exchange Server versions
• Recovers deleted exchange mailbox  
• Facilitates archive mailbox recovery
• Can recover selective exchange mailbox  
• Prioritizes Mailbox Recovery
• Repairs large EDB files quickly and efficiently

You may download and use the free trial version of this exchange EDB recovery tool to scan and preview the recoverable contents of the Exchange mailboxes. Alternatively, go on to buy the Corporate, Technician, or Toolkit editions of Stellar Repair for Exchange subject to your specific requirements. 

A proficient tool for Exchange Database Recovery, it holds recommendations from MVPs. It is beyond doubt, feasible software to help you resolve the Content index state suspended state as well.

Conclusion

Content index state suspended is a common issue in Exchange 2016. It may happen due to data migration to a new server, storage issues, improper installation of the latest Cumulative Update and antivirus software, etc. 

While this error does not affect the email exchange adversely, it does create problems in searching for the mailboxes. If you want to connect to Outlook Web Application (OWA) to look for the contents in a specific mailbox, you may encounter this Content index state suspended or failed error. 

You may resolve this issue depending on whether the Exchange 2016 is the standalone server or is a part of the Data Availability Group (DAG). Using PowerShell cmdlets would help to execute the requisite command in both these cases. If the problem prevails, you may go through a checklist of do’s and don’ts. Using the ESEUTIL utility tool is one of them. 

A comparably better, safer, and quicker method compared to manual resolutions is to use an Exchange EDB recovery tool such as Stellar Repair for Exchange. A popular software embraced by small and big corporate hubs, it can repair the database and export the recovered data to a new Exchange mailbox database, PST, or Office 365.