Forum Discussion
Content Index Update Failed
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.
Hi simsumm,
thanks for the update.
You can try these additional steps:
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)
- simsummNov 25, 2023Copper Contributor
LeonPavesic, thank you. I will try the database repair and revert back to share the outcome.