Forum Discussion

simsumm's avatar
simsumm
Copper Contributor
Nov 21, 2023

Content Index Update Failed

[PS] C:\Windows\system32>Update-MailboxDatabaseCopy -CatalogOnly -SourceServer topinc-exh04 -Identity db6\topinc-exh01

Confirm
Are you sure you want to perform this action?
Seeding database copy "db6\topinc-EXH01".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): A
WARNING: Seeding of content index catalog for database 'db6' failed. Please verify that the Microsoft Search (Exchange)
and the Host Controller service for Exchange services are running and try the operation again. Error: There was no
endpoint listening at net.tcp://localhost:3863/Management/SeedingAgent-2D077D5D-A4EB-4B63-98C6-42861CF38C2312/Single
that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if
present, for more details...

 

All Exchange Services are running

 

Suggestions on how to resolve this issue will be appreciated.

2016
Exchange Server

4 Replies

Sort By
  • LeonPavesic's avatar
    LeonPavesic
    Silver Contributor
    Nov 21, 2023

    Hi simsumm,

     

    It appears that you're dealing with a content index issue on your Exchange Server 2016.

    To address this problem, consider the following steps:

    1. Verify Content Index Status:
    Use the Exchange Management Shell to check the content index status with the command:

    Get-MailboxDatabaseCopyStatus * | Select Name,*index*

    If the `ContentIndexState` shows as `Failed` or `FailedAndSuspended`, it's advisable to rebuild the index.

    2. Rebuild Content Index:
    If you're not utilizing a Database Availability Group (DAG), follow these steps:
    - Stop the search services:

    Stop-Service MSExchangeFastSearch
Stop-Service HostControllerService


    - Delete the folder containing the content index files.
    - Start the search services again:

    Start-Service MSExchangeFastSearch
Start-Service HostControllerService


    Allow time for the content index to rebuild, considering the database size.

    3. Reseed Content Index:
    For DAG users, reseed the content index from a healthy copy:

    Update-MailboxDatabaseCopy -Identity "YourDatabaseName\YourServerName" -CatalogOnly


    Once the content index has completed rebuilding or reseeding, you should observe healthy results.

     

    You can use these links as a reference:
    - [Kernel Data Recovery] https://www.kerneldatarecovery.com/blog/resolve-exchange-database-content-index-state-failed/
    - [Practical 365] https://practical365.com/exchange-2016-failed-content-index/
    - [Frankys Web] https://www.frankysweb.de/exchange-20132016-index-neu-erstellen/

    Please click Mark as Best Response & Like if my post helped you to solve your issue.
    This will help others to find the correct solution easily. It also closes the item.


    If the post was useful in other ways, please consider giving it Like.


    Kindest regards,


    Leon Pavesic
    (LinkedIn)

    • simsumm's avatar
      simsumm
      Copper Contributor
      Nov 22, 2023

      LeonPavesic,Thank you for your recommendations. I have tried them all; my environment is DAG 2016 with 4 nodes. There are 20 databases, but only one is experiencing this issue.

      • LeonPavesic's avatar
        LeonPavesic
        Silver Contributor
        Nov 22, 2023

        Hi simsumm,

        thanks for the update.

        You can try these additional steps:

        1. Review Replication Logs: Examine the replication logs for any errors or delays related to the specific database. You can use the following command to check the replication status:

         

        Get-MailboxDatabaseCopyStatus -Identity "YourDatabaseName" | fl

         

        Look for any errors or warnings in the logs.

        • Database Repair: If the issue persists, you may consider running a database repair. However, be cautious as this process involves dismounting the database and may result in downtime. Ensure that you have a recent backup before attempting any repair operations.

         

        Dismount-Database "YourDatabaseName" Repair-Database "YourDatabaseName" -DetectOnly

         

        If issues are detected, you can run the repair without the -DetectOnly switch.

         

        Please click Mark as Best Response & Like if my post helped you to solve your issue.
        This will help others to find the correct solution easily. It also closes the item.


        If the post was useful in other ways, please consider giving it Like.


        Kindest regards,


        Leon Pavesic
        (LinkedIn)

Resources