How to Get Rid of Exchange Server is in an Inconsistent State?
Summary: While working on the Microsoft Exchange Server 2016/2013/2010, sometimes users are caught with this error i.e. Exchange Server is in an inconsistent state. This write-up will guide users on how to troubleshoot the error by using the best possible solution.
As we all know the Microsoft Exchange Server is an essential part of the IT organization and other industry verticals whether it is large, small, or medium for business purposes. It is the most reliable mail server that made it possible to carry out communication inside and outside of the organization and vice-versa.
It provides variously specialized as well as advanced services for the users. One of the responsibilities of an administrator involves upgrading or reinstalling the Exchange Server whenever it is damaged or its support ends.
How does an Inconsistent State in the Exchange Server Occurs?
When the MS Exchange Server object is already there in the Active Directory while users uninstalled the previous Exchange Server version and then try to upgrade or reinstall the MS Exchange latest server version.
The Exchange Server generally encounters the inconsistent state error when the previous releases that is something which is not possible to resolve by using the latest patches as well as bug fixes that are released in the updated service packs.
So, Microsoft Exchange Administrators should be well aware of the fact that they should be ready for any disaster that will occur on the server.
Solutions to Solve The Exchange Server Is In Inconsistent State Error
Once your Exchange Server is in an inconsistent state, you have to go for the disaster recovery mode as recommended by experts. However, it is not an easy task as it requires setting up a new Exchange Server which is itself a time-consuming task.
Thus, if you don’t wish to go with the Disaster recovery mode, then you should remove the Exchange Server object from Active Directory before initiating the update/reinstallation task.
Solution 1: Rename the New Exchange Server Version
This is the easiest, simple, and most suitable way to troubleshoot the error. Follow the method given below:
- Rename the new Microsoft Exchange Server name with a unique name. Remember that the new server name is completely different from the previous one.
- Join the Exchange Server with the domain name.
- Install the MS Exchange Server to fix the error.
Solution 2: Reinstall Microsoft Exchange Server In Recovery Mode
When this error occurs in Exchange, users try to rebuild the Microsoft Exchange Server in recovery mode with the same name by using the configuration that is stored in the AD (Active Directory) of that inconsistent server.
In this process, users can use the Setup /m:RecoverServer switch that will help them to rebuild a damaged server in recovery mode automatically.
Point to be Noted: The following groups should have the Exchange account as a part of them.
- Domain Admins Group
- Enterprise Admins Group
- Exchange Organization Management Group
Follow the steps to rebuild the Exchange Server using recovery mode:
Step 1: Disable the UAC (User Account Control) on Microsoft Exchange Server
Step 2: Locate Exchange Setup File and Run it in Recovery Mode
Step 3: Run the Following Command in PowerShell:
.\setup.exe /m:recoverserver/iacceptexchangeserverlicenseterms
Note: “recoverserver” switch enables the rebuilding process with the help of parameters that are stored in AD.
Step 4: After completing the setup, reconfigure the settings as per your need and restart the Exchange Server.
Solution 3: Delete Microsoft Exchange Server Object & Relaunch Exchange Setup
Permanently delete all objects from AD and then re-install the new version to fix the error:
1. Open the run dialogue box by pressing Win + R key > type ADSIEdit.msc > click on the OK button.
CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=<Your Organization Name>, CN=Administrative Groups, CN= <Exchange 2010 Administrative Group>, CN=Servers, CN=<Server Name>
2. Now find the Exchange Server object and delete it.
3. Following that, wait for the changes to be synchronized in Active Directory.
4. Relaunch Exchange Setup for upgrade or reinstallation.
If your Exchange Server is still in an Inconsistent state, then there might be an issue with the Exchange database and not the Exchange Server. A damaged Exchange DB can cause numerous issues in the smooth working of the server. You can try the following utility to get rid of the corruption issues.
Try This Solution if There are Signs of Corruption
There can be n number of reasons for a damaged Exchange database like Exchange database’s dirty shutdown state, hardware failure, sudden power loss, etc. In such cases, the Exchange administrators must go for the best-rated Exchange Database Recovery Tool. The two recovery modes offered in this utility make it quite easy for the users to get rid of corruption.
This smart solution helps users to repair damaged EDB files in just no time. The advanced algorithms used in this software help in the in-depth recovery of databases and get back our data in a healthy state.
After successful recovery, users can either import EDB files into Exchange Server or export them into multiple file formats including PST, PDF, MBOX, MSG, etc. The software is compatible with Exchange Server 2016, 2013, 2010, 2007, or lower versions.
Conclusion
This article provides detailed information to fix Exchange Server’s inconsistent state error. Now users know each and every detail of why this error occurs and how to resolve it. However, there might be a chance that this solution doesn’t work to fix the problem and the reason behind the Exchange database file and mailboxes being damaged or corrupted. For such instances, a smart solution for the same is also discussed.
