
Exchange database content index state failed
24 November 2019Problem
The index status of the database is failing. It can be verified via the command Get-MailboxDatabaseCopyStatus

Resolution
If a DAG is present, we will cut the copy:
1 | Suspend-MailboxDatabaseCopy – Identity dbname\exchangeserver2 |
We will stop indexing services
1 2 | Stop–Service MSExchangeFastSearch Stop–Service HostControllerService |
We go to the directory where the database is stored.

we will delete the directory with a GUID
We will start indexing services
1 2 | Start–Service MSExchangeFastSearch Start–Service HostControllerService |
We will update the catalog on the passive server (if a DAG is present)
1 | Update-MailboxDatabaseCopy - Identity dbname\exchangeserver2 -SourceServer exchangeserver1 -CatalogOnly |
We will check the status of the databases via the command:
Get-MailboxDatabaseCopyStatus
Views: 502