So we came across this when attempting a “Move-ActiveMailboxDatabase” powershell command to mount a mailbox database copy in our DAG. We have a powershell script that mounts all DBS on one exchange server so we can do maintenance on the other. 

Some Database copies were not mounting and the powershell cmdlet displayed something similar to the following error:-

An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy ‘database′ on server ‘exchserver1’ has content index catalog files in the following state: ‘Failed’. [Database: mydb, Server: exchserver2]

An Active Manager operation failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy ‘database′ on server ‘exchserver1’ has content index catalog files in the following state: ‘Failed’.

So we can understand from this error that the Index Catalog on the destination exchange server mailbox database is corrupt. One of the first things we tried was to run the “Get-MailboxDatabaseCopyStatus” powershell command to check the status of the catalog:-

Name : mydbmyexchangeserver1
ContentIndexState : Failed

So we can see we definitely have  a failed index on our mailbox database.

There are a couple of ways to reseed the Index as described in thisMicrosoft Technet KB. The following method fixed our catalog:-

This powershell command will reseed the Index Catalog from any available exchange server in the DAG. To be more specific, you can target a specific exchange server by running:-

Re-run the Get-MailboxDatabaseCopyStatus cmdlet as above and your index catalog should now be healthy.

There are other methods to rebuild the index catalog, one common approach is to delete the index catalog folder and restart the Exchange Search Service on the Exchange Server.

Leave a Reply

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