Pages

Tuesday, January 5, 2016

Troubleshoot: Exchange Server Is In an Inconsistent State - Exchange 2013 Condition

Microsoft Exchange Server is the lifeline of most large and medium sized businesses. With its exceptional services, the server has made it possible for organizations to carryout inbound and outbound communication from their domain. A number of specialized services are additionally provided for Exchange by Microsoft in order to make the experience exceptionally convenient for users along with the administrator. Administrators are highly benefitted by the server due to its ability of simplifying administrative activities like; mailbox archiving, message sending, reporting message delivery, and more. One such acts as the solution to a condition where Exchange Server is in an inconsistent state. Exchange 2013 being the commonly used version amongst the latest releases is targeted in this segment for sharing the solution to one of the most common technical glitches surfaced in Exchange.

What Brings Exchange Server In An Inconsistent State?

Exchange has been encountering inconsistent state since its previous releases and that is something unresolvable via the latest patches and bug fixes releases in each of the updated service packs. Therefore, administrators must be prepared for any scenario that leads to a disaster or probably could. Thus, the segment shares some of the commonly encountered errors that are surfaced in a similar condition. The information is accompanied by resolutions that are applicable in order to troubleshoot the condition.

How It All Begins?

During an installation of Exchange Server it is probable that due to lack of system requirement fulfillment or other similar reasons the process may fail. The installation process when encounters a failure it makes the server go into an inconsistent state preventing it from initiating. In a case like this, you might have to re-install the Exchange Server 2013 with the help of recovery mode.
Recovery Mode: Exchange Servers all across the globe function in a setup of distributed systems. This kind of setup architecture offers the server to have an excellent level of resiliency. Moreover, majority of Exchange configurations are stored apart from the server on the AD. The distributed setup ensures that rebuilding of the damaged server completely automatic.

System Requirements:

  1. You need to disable the User Account Control on Exchange Server
  2. Now open PowerShell and reach out to the location storing the setup file
  3. Once you have reached, perform the following command run:
    • .\setup.exe /m:recoverserver/iacceptexchangeserverlicenseterms
    • The switch ‘recoverserver’ will enable rebuilding of Exchange server with the help of the parameters that are stored within the Active Directory
NOTE: The account using which you are supposed to perform the Exchange recovery must come under the following groups:
  1. Domain Admins Group
  2. Enterprise Admins Group
  3. Exchange Organization Management Group
Conclusion: The resolution and workarounds discussed above are the best for troubleshooting when Exchange Server is in an inconsistent state. Exchange 2013 is specifically taken in example in this particular case to explain the scenario. Ensure that the listed system requirements are successfully fulfilled in order to carry out the troubleshooting process without failure. Exchange Recovery mode is the best way to fix the issue in a successful manner. In case of not receiving a successful output, leave a comment.

Thanks for Reading
Tej Pratap Shukla
Exchange Server Expert




Visit my last post which I have written about Edge Transport Server Planning and Configuration for Internet Mail Flow.
Keep visiting my Exchange Server Blog to keep yourself updated about Exchange Server and Office 365.

0 comments:

Post a Comment

Post a reply