locked
After upgrading to Ex2013 CU23 indexing of all databases are in failed state RRS feed

  • Question

  • Hi All

    Need assistance regarding the above issue. Unable to bring the indexing state to healthy after upgrading to CU23.

    Tried deleting the content index folder of each database and start the service.

    Tried updating using catalog only option

    even tried rebuilt the database using delete existing files. 

    But still the issue persists.

    Sunday, June 7, 2020 5:03 AM

All replies

  • Sunday, June 7, 2020 1:25 PM
  • Thank you Nagarajan for the suggestion.

    Our servers are in DAG. So already performed the steps provided in the below article:

    https://practical365.com/exchange-server/fix-all-failed-exchange-database-content-indexes/

    But still the same.

    Sunday, June 7, 2020 2:57 PM
  • Hi,

    Here are more suggestions for index issue:

    1. Use the following command to make sure IndexEnabled parameter is set to true for all databases:

    Get-MailboxDatabase | Format-Table Name,IndexEnabled

    2. Check mailbox database crawl state. Go to Performance Monitor > Monitoring Tools > Performance Monitor > Add Counters, select the server on which the mailbox database you want to monitor is located

    Then select the MSExchange Search Indexes performance object, and the instance for the database:

    View the Crawler: Mailboxes Remaining counter. Any value of 1 or higher indicates that mailboxes in the database are still being crawled. When the crawl is complete, the value is 0:

    3. Restart the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services. Then reseed the content index catalog again to see if any differences. Since it may take some time to rebuild the index catalog, please wait for a while to check:

    Update-MailboxDatabaseCopy -Identity DB_name\MBX_name -SourceServer servername -CatalogOnly

    4. Check Event Viewer to see any related event logs for further analysis.

    Additionally, if it's convenient, please post the screenshot or copy the output of following command here, and don't forget to cover your personal information:

    Get-MailboxDatabaseCopyStatus *

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, June 8, 2020 6:02 AM
  • Hi Lydia

    Thank you for the steps provided. Please find the below details:

    1. IndexEnabled parameter is set to TRUE for all databases

    2. mailbox database crawl state --> Mailboxes Remaining counter is 0 for all.

    3. Restarted the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services. Then reseeded the content index catalog again but still in failed state.

    4. Check Event Viewer --> Event ID 1009 (MSExchangefastsearch), 1310 (asp.net 4.0.30319.0)

    Planning to run CU23 again. 

    Thanks 

    Wednesday, June 10, 2020 10:51 AM
  • You can post the screenshot of the event logs here for further analysis, and don't forget to cover your domain name and other personal information.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, June 11, 2020 8:37 AM
  • Any updates so far?

    If you have solved your problem, could you share with us? Maybe it will help more people with similar problems. 

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, June 15, 2020 8:56 AM
  • Suppose, problem in FAST Search
    This article may help:
    https://social.technet.microsoft.com/wiki/contents/articles/31215.exchange-2013-fast-search-technology-failed.aspx
    Wednesday, June 17, 2020 7:27 PM
  • Hello Lydia

    Currently, for this issue raised a call with Microsoft. But support is too slow.

    However, I will update all steps.

    Regards

    Abhi

    Thursday, June 18, 2020 4:02 AM
  • Hello Jurec,

    Thanks for the article. It's the exact steps that MS asked to perform. 

    Waiting for management approval before performing it in production server.

    Will update if it was successful.

    Regards

    Abhi

    Thursday, June 18, 2020 4:07 AM
  • Hello Lydia

    Currently, for this issue raised a call with Microsoft. But support is too slow.

    However, I will update all steps.

    Regards

    Abhi

    That's Ok. Hope your issue can be solved soon.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, June 18, 2020 6:58 AM
  • Call with Microsoft still in place. They are unable to identify the issue.

    last update: MS asked to copy complete search folder from working server to the impacted server. But we cannot rename the search folder on impacted server. It say's the folder is in use. All MS services were stopped. AV and Backup were disabled. Microsoft cannot explain that. As per them some indexing issue may take months to resolve. This is similar issue. Waiting for further updates.

    Sunday, July 5, 2020 2:28 PM
  • Well, if available, you also can install a new Exchange 2013 CU23 to replace that problematic server. If a new cumulative update can be released in the future, you can install the latest CU again and check if the issue can be fixed automatically in the upgrade.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, July 6, 2020 8:31 AM