none
How To Fix Failed Exchange Database Content Indexeing On A Lagged Database

    Question

  • Hi All,

    I have a Lagged Copy Exchange 2010 Database.

    The Content Index Is In a failed state and I need to resync it.

    When I use the Update-MailboxDatabaseCopy "MBX\SERVER" -CatalogOnly nothing happens.

    Can someone tell me please how do I fix the failed content Indexing on a Lagged Exchange 2010 DB ?

    Cheers,


    Exchange Blog:

    www.ntweekly.com

    MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

    Monday, July 20, 2015 10:49 PM

Answers

  • What do you mean by nothing happens, it doesn't even try to seed the content index database from a good server?

    I would also try following...

    1. Restart the "Microsoft Exchange Search Indexer" service and wait for a while and see if it helps...

    2. Stop the "Microsoft Exchange Search Indexer" serive

    Delete the content index / catalog folder of each database

    Start the service back and wait for a while to get the index db updated from a good server...


    Amit Tank | Exchange - MVP | Blog: exchangeshare.wordpress.com 

    Monday, July 20, 2015 10:59 PM
    Moderator
  • Hi Shimon1,

    Thank you for your question.

    I agree with Amit. We could refer to the steps which Amit supplied to check if the issue persist. It just rebuild context index and don’t have any effects on production.

    https://technet.microsoft.com/en-us/library/aa995966(v=exchg.80).aspx (it also apply to Exchange 2010)

    If the issue persist, we could check if there are any errors in application log and post them for our troubleshooting.

    If there are any questions regarding this issue, please be free to let me know.

    Best Regard,

    Jim


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Tuesday, July 21, 2015 9:25 AM
    Moderator

All replies

  • What do you mean by nothing happens, it doesn't even try to seed the content index database from a good server?

    I would also try following...

    1. Restart the "Microsoft Exchange Search Indexer" service and wait for a while and see if it helps...

    2. Stop the "Microsoft Exchange Search Indexer" serive

    Delete the content index / catalog folder of each database

    Start the service back and wait for a while to get the index db updated from a good server...


    Amit Tank | Exchange - MVP | Blog: exchangeshare.wordpress.com 

    Monday, July 20, 2015 10:59 PM
    Moderator
  • Hi There,

    When I say nothing happens I mean that when I issue the cmdlet there is no change in the screen (no progress , no error).

    I'm looking to a fix that will not require restart of services and deleting files.

    Cheers,


    Exchange Blog:

    www.ntweekly.com

    MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

    Monday, July 20, 2015 11:26 PM

  • When I say nothing happens I mean that when I issue the cmdlet there is no change in the screen (no progress , no error).


    That's strange part, it should at least prompt you with error if something is wrong in the cmdlet or "DBName\ServerName" format or if DB has only one copy....

    Did you try re-opening the Exchange Management Shell?

    Restarting Microsoft Exchange Search Indexer" doesn't hurt and in many cases you have to do it if updating content index doesn't work, it might even fixes without updating the content index from other server, by just restarting service (have seen that case), what if search indexer process is hosed up...


    Amit Tank | Exchange - MVP | Blog: exchangeshare.wordpress.com 

    Monday, July 20, 2015 11:35 PM
    Moderator
  • Hi Shimon1,

    Thank you for your question.

    I agree with Amit. We could refer to the steps which Amit supplied to check if the issue persist. It just rebuild context index and don’t have any effects on production.

    https://technet.microsoft.com/en-us/library/aa995966(v=exchg.80).aspx (it also apply to Exchange 2010)

    If the issue persist, we could check if there are any errors in application log and post them for our troubleshooting.

    If there are any questions regarding this issue, please be free to let me know.

    Best Regard,

    Jim


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Tuesday, July 21, 2015 9:25 AM
    Moderator