Forum Discussion
Exchange 2016 Database Copy Status Shows "Unknown" in ECP
Exchange 2016 Database copy status in ECP shows as "Unknown" in ECP but shows as "Healthy" in Exchange Management Shell.
Suggestions on how to resolve this issue will be appreciated.
3 Replies
Hi simsumm,
This issue may arise for various reasons, including recent database updates, database corruption, or hardware issues.
Here are some suggestions to address this problem:1. Remount the Exchange database:
- In the Exchange Admin Center (EAC), navigate to 'servers' and click on 'databases.'
- Choose the Exchange database with an unknown status, click 'More Options,' and select 'Mount' to remount the database.
- Alternatively, you can use PowerShell and run the Mount-Database cmdlet in the Exchange Management Shell (EMS) as an administrator.2. Restart Microsoft Exchange Services:
-On your Exchange Server system, open the Run box (Windows key + R), type services.msc, and click OK.
- Locate the essential Microsoft Exchange Services, select each one, and choose 'Restart' from the drop-down list.
- to find a list of all essential Exchange services or even to restart them with PowerShell, you can use this useful article:
Restart Exchange Server services through PowerShell - ALI TAJRAN3. Restart the Exchange Server:
occasionally, changes made to the server or database, such as renaming the database, may not take effect without restarting the server.www.nucleustechnologies.com
www.stellarinfo.com
www.stellarinfo.co.in
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)LeonPavesic, thank you for your recommendations. I have tried them all. The latest thing I tried was to create a new database. It mounted successfully using the Shell but shows as "Unknown" in ECP.
I have rebooted all 4 DAG nodes multiple times including the Domain Controllers but no luck. The environment has been running for about 3 years and we have never had this kind of experience before. Further suggestions from the community on how to resolve this will be appreciated.
