Monday 23 June 2014

Steps To Solve Content Index Failed Error

Steps To Solve Content Index Failed Error

If content index is in failed, and you try activating database copies during database switchover, it will fail. To solve the problem perform below steps to repair the content index.

    1.Log in to particular server on which content index has failed.
    2.Log in to EMS and run below command to verify the content error.

    Get-MailboxDatabase Database Name | Get-MailboxDatabaseCopyStatus | Select Name,*index*
    EG: Get-mailboxdatabase Database1 | get-mailboxdatabasecopystatus | select name, *index*

    3.Now run to below command to repair catalog of affected database.

    Update-MailboxDatabaseCopy Database Name** –sourceserver Server Name* –catalogonly
    EG :Update-MailboxDatabasecopy Database1\Server1 –sourceserver Server2 –catalogonly

    Note : * Server name on which content index is in healthy state.
    ** Database name in format : Database1\Server1
    Updating of catalog will take sometimes depend upon catalog size. 

     4.Follow steps 1-3 to for all unhealthy copies.

    5.After that verify it once again by below command if content Index State is changed to healthy.

    Get-MailboxDatabase Database Name | Get-MailboxDatabaseCopyStatus | Select Name,*index*
    EG: Get-mailboxdatabase Database1 | get-mailboxdatabasecopystatus | select name, *index*






       



















     

No comments:

Post a Comment