What are the Reasons for Content Index “Failed” and “Suspended” Error?<\/h2>
Here are some possible reasons that can lead to this error:<\/p>
- \n
- This issue might occur during migration from an older version of Exchange Server<\/strong> or due to a problem of storage space<\/strong>.<\/li>\n\n\n\n
- Issues might occur post installation of the latest Cumulative Update (CU)<\/strong> either to a bad update or wrongfully installing an incompatible version.<\/li>\n\n\n\n
- The server ended with no disk space where the database is stored and ended up with a failure<\/strong> on the index.<\/li>\n\n\n\n
- Antivirus software<\/strong> which is not compatible with the Exchange Server installed or wrongly configured<\/strong>, can lock the Exchange Server files, and stop the indexing from working successfully. It’s important to not have an aggressive configuration as this might disrupt the system.<\/li>\n\n\n\n
- The replication is not working fine in a Database Availability Group (DAG)<\/strong> as this would also affect the indexing and of course the data in case of a failover.<\/li>\n<\/ul>
How to Identify “Content Index State Failed and Suspended” Error?<\/h2>
If the issue has been reported by the users that they cannot search in their mailboxes, the only way to identify the issue is by checking the mailbox database copy status.<\/p>
For this, you can use the PowerShell cmdlet – Get-MailboxDatabaseCopyStatus in the Exchange Management Shell (EMS).<\/p>
Get-MailboxDatabaseCopyStatus * | sort name | Select name,status,contentindexstate<\/code><\/code><\/pre>\n![\"Get-MailboxDatabaseCopyStatus](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/Get-MailboxDatabaseCopyStatus-1.png\")
<\/figure>\n<\/div>This will show the status of the databases and the content index state. If the state shows FailedAndSuspended<\/strong>, then you need to intervene to resolve the problem.<\/p>
How to Resolve ‘Content Index State Failed and Suspended’ Error in Single Exchange Server Setup?<\/h2>
When your Exchange Server is a standalone server and is not part of a Database Availability Group (DAG), you can rebuild the content index by following the below procedure.<\/p>
\n
Note:<\/strong> Although this is a simple procedure, you might end up with performance degradation on the server as it is very resource-hungry on the CPU utilization. It is strongly suggested to run this process during a maintenance window or at night or on a weekend.<\/em><\/p>\n<\/blockquote>
- \n
- The first step is to stop the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller services.<\/li>\n<\/ul>\n
![\"Exchange](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/exchange-services-2.png\")
<\/figure>\n<\/div>- \n
- This can be done from the services.msc.<\/strong> For this, right-click on the service and then click on stop. Alternatively, this can be done from PowerShell by using the Stop-Service<\/strong> cmdlet (as given below).<\/li>\n<\/ul>
Stop-Service MSExchangeFastSearch
Stop-Service HostControllerService<\/code><\/code><\/pre>![\"Stop-Service](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/stop-exchange-services-3.png\")
<\/figure>- \n
- The next step is to delete the content index from the path of the database. This can be done by using File Explorer<\/strong>. For this, browse to the folder where the EDB file is stored which corresponds to the database with the problem, and delete the folder with the GUID.<\/li>\n<\/ul>\n
![\"delete](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/delete-the-content-index-4.png\")
<\/figure>\n<\/div>- \n
- Make sure that the services mentioned above are stopped. Otherwise, you will not be allowed to delete the folder. If you are unsure of the file path, you can use the PowerShell cmdlet – Get-MailboxDatabase<\/strong><\/a> to get the file path of the database.<\/li>\n<\/ul>
Get-MailboxDatabase <database name> | select EdbFilePath<\/code><\/code><\/pre>\n![\"Get-MailboxDatabase](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/Get-MailboxDatabase-5.png\")
<\/figure>\n<\/div>- \n
- After you have deleted the folder of the content index, start the services as given below.<\/li>\n<\/ul>\n
![\"start](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/start-exchange-services-6.png\")
<\/figure>\n<\/div>- \n
- You can also use the below PowerShell cmdlet to start the services.<\/li>\n<\/ul>
Start-Service MSExchangeFastSearch
Start-Service HostControllerService<\/code><\/code><\/pre>- \n
- Now, the services will start crawling and indexing all the content of the database. The indexing may take some time to complete, depending on the size and number of items of the database. Once this is done, re-run the Get-MailboxDatabaseCopyStatus PowerShell cmdlet<\/a><\/strong>. You will see the database state as healthy.<\/li>\n<\/ul>\n
![\"database](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/Get-MailboxDatabaseCopyStatus-state-7.png\")
<\/figure>\n<\/div>How to Fix ‘Content Index State Failed and Suspended’ Error in DAG Setup?<\/h2>
To fix ‘Content Index State Failed and Suspended’ error in DAG setup, follow the steps given below:<\/p>
When your database is in a Database Availability Group (DAG),<\/strong> you need to run the re-seeding of the database from a healthy database copy<\/a>. This can be done by using the Update-MailboxDatabaseCopy PowerShell cmdlet (as given below).<\/p>
Update-MailboxDatabaseCopy <database name>\\<source server name> -CatalogOnly -BeginSeed<\/code><\/code><\/pre>\n![\"Database](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/Update-MailboxDatabaseCopy-8.png\")
<\/figure>\n<\/div>- \n
- This operation may take time, depending on the connection between the servers and the size of the database. Once the operation is complete, re-run the Get-MailboxDatabaseCopyStatus<\/strong> PowerShell cmdlet. You will see the ContentIndexState <\/strong>as healthy.<\/li>\n<\/ul>\n
![\"ContentIndexState](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2021\/02\/ContentIndexState-healthy-9.png\")
<\/figure>\n<\/div>What to do if the Issue still Persists?<\/h3>
If the fixes mentioned above didn’t help in resolving the ‘Content Index State Failed and Suspended’ error, you can follow the below troubleshooting steps:<\/p>
- \n
- Make sure you have installed latest update of Exchange server<\/strong> after checking the Microsoft site.<\/li>\n\n\n\n
- Restart the Exchange Server<\/strong> to ensure that any pending configuration <\/strong>changes, or updates are committed.<\/li>\n\n\n\n
- Also make sure that you have enough HDD space<\/strong> on the drive that the database\/index<\/strong> is on for a copy\/expansion.<\/li>\n\n\n\n
- Make sure you’ve configured antivirus exclusions<\/strong> for the database, logs, and indexes.<\/li>\n\n\n\n
- Also try simplifying your networking by removing the replication network<\/strong> if not needed.<\/li>\n\n\n\n
- Create new Exchange database and move the mailboxes to the new DB<\/strong>, as the index will be recreated automatically on the new DB.<\/li>\n<\/ul>
Also Read:<\/strong> How to Fix “Exchange Database Status Unknown<\/a>?”<\/p>
To Conclude<\/strong><\/h2>
While the above-given solutions resolve the issue, this does not mean that they will work every time. If the issue occurs on a regular basis, it indicates corruption in the database. If this is the case, you can use the Exchange native tools, such as ESEUtil<\/a>, to run a database recovery process. However, to do so, the database must be offline.<\/p>
Alternatively, you can use Stellar Repair for Exchange<\/strong> to repair the corrupt database and export all mailboxes to PST or to a live Exchange database. This tool allows you to browse through the whole database – mailboxes, contacts, calendar, tasks, and journal. By using the Exchange recovery software<\/a>, you can also export the mailboxes directly to an Office 365 (Microsoft 365) tenant. This tool supports databases created in Exchange Server Subscription Edition (SE), 2019, 2016, 2013, and earlier versions.<\/p>\n","protected":false},"excerpt":{"rendered":"
- Restart the Exchange Server<\/strong> to ensure that any pending configuration <\/strong>changes, or updates are committed.<\/li>\n\n\n\n
- Make sure you have installed latest update of Exchange server<\/strong> after checking the Microsoft site.<\/li>\n\n\n\n
- This operation may take time, depending on the connection between the servers and the size of the database. Once the operation is complete, re-run the Get-MailboxDatabaseCopyStatus<\/strong> PowerShell cmdlet. You will see the ContentIndexState <\/strong>as healthy.<\/li>\n<\/ul>
- Now, the services will start crawling and indexing all the content of the database. The indexing may take some time to complete, depending on the size and number of items of the database. Once this is done, re-run the Get-MailboxDatabaseCopyStatus PowerShell cmdlet<\/a><\/strong>. You will see the database state as healthy.<\/li>\n<\/ul>
- You can also use the below PowerShell cmdlet to start the services.<\/li>\n<\/ul>
- After you have deleted the folder of the content index, start the services as given below.<\/li>\n<\/ul>
- Make sure that the services mentioned above are stopped. Otherwise, you will not be allowed to delete the folder. If you are unsure of the file path, you can use the PowerShell cmdlet – Get-MailboxDatabase<\/strong><\/a> to get the file path of the database.<\/li>\n<\/ul>
- The next step is to delete the content index from the path of the database. This can be done by using File Explorer<\/strong>. For this, browse to the folder where the EDB file is stored which corresponds to the database with the problem, and delete the folder with the GUID.<\/li>\n<\/ul>
- This can be done from the services.msc.<\/strong> For this, right-click on the service and then click on stop. Alternatively, this can be done from PowerShell by using the Stop-Service<\/strong> cmdlet (as given below).<\/li>\n<\/ul>
- Issues might occur post installation of the latest Cumulative Update (CU)<\/strong> either to a bad update or wrongfully installing an incompatible version.<\/li>\n\n\n\n