locked
Exchange Server 2013 Setup -- "Inconsistent State" error when initializing setup files RRS feed

  • Question

  • I am creating my first Exchange 2013 server DAG complete with its own dedicated Active Directory in my lab. Currently, I have 4 servers in the domain all running Windows 2012 Datacenter: 1 AD server and 3 Exchange servers (two of which will be configured with just mailbox database role/added to the DAG and the third which is a dedicated CAS as well as my FSW that will not be included in the DAG). Here are the steps I took:

    1. Installed Windows 2012 AD successfully on server1.
    2. Successfully installed Exchange 2013 (Mailbox Database only) on server2.
    3. Successfully installed Exchange 2013 (CAS only) on server3.
    4. Configured server3 for FSW by adding Exchange Trusted Subsystem to local Administrators group. (only DAG configuration I did)

    5. Attempted installation of Exchange 2013 (Mailbox Database only) on server4. Upon "Setup Initializing", I was met with this error message:

    "The Exchange Server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer to recover this server"

    6. Ran clean installation of Windows 2012 on this box and removed the server's computer account from AD, re-added server to AD with same computer name.
    7. Ran all required prerequisites for Exchange 2013 and attempted reinstallation -- this time using ./setup.exe /m:RecoverServer. Installation failed again. This time, prerequisite analysis failed:

    "Disaster recovery setup needs access to the log drive '[default path to mailbox database directory]' to continue."

    "Disaster recovery setup needs access to the mailbox database drive '[default path to mailbox database directory] to continue."

    ....along with the standard send connector wildcard prerequisite error (haven't set up a send connector yet) that I've experienced on all Exchange 2013 installs I've done thus far.

    I checked the ExchangeSetup.log which reported this additional error:
    "The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found"

    I formatted this machine and reinstalled 2012 3 times already.

    Any suggestions? Did I do something wrong? Do I have to scrap all of my previous installations in this environment before this will work properly?

    Friday, November 15, 2013 5:43 PM

Answers

  • Hi Hybrid,

    About Error "The Exchange Server is in an inconsistent state. Only disaster recovery mode is available.", it is recommended to remove the Exchange server object in Active Directory for troubleshooting.

    If the previous Exchange 2013 installation failed to complete, it leaves the Exchange 2013 server object in Active Directory and prevents a new Exchange 2013 installation.

    Hope my clarification is helpful.

    Best regards,
    Amy


    Amy Wang
    TechNet Community Support

    • Marked as answer by cara chen Wednesday, November 20, 2013 9:55 AM
    Monday, November 18, 2013 8:01 AM
  • Just formatted the server and reinstalled 2012, ran through the prerequisites, but this time I used a different computer name and the Exchange 2013 install went smoothly. Odd.

    Any suggestions as to why this is? Am I setting myself up for future problems with the old server name floating around in AD somewhere? I checked ADSI and AD Users & Computers and deleted all instances of the previous server name.


    • Edited by HybridMoments82 Friday, November 15, 2013 8:56 PM
    • Proposed as answer by Mike Crowley Friday, November 15, 2013 9:51 PM
    • Marked as answer by cara chen Wednesday, November 20, 2013 9:55 AM
    Friday, November 15, 2013 8:56 PM

All replies

  • Just formatted the server and reinstalled 2012, ran through the prerequisites, but this time I used a different computer name and the Exchange 2013 install went smoothly. Odd.

    Any suggestions as to why this is? Am I setting myself up for future problems with the old server name floating around in AD somewhere? I checked ADSI and AD Users & Computers and deleted all instances of the previous server name.


    • Edited by HybridMoments82 Friday, November 15, 2013 8:56 PM
    • Proposed as answer by Mike Crowley Friday, November 15, 2013 9:51 PM
    • Marked as answer by cara chen Wednesday, November 20, 2013 9:55 AM
    Friday, November 15, 2013 8:56 PM
  • Hi Hybrid,

    About Error "The Exchange Server is in an inconsistent state. Only disaster recovery mode is available.", it is recommended to remove the Exchange server object in Active Directory for troubleshooting.

    If the previous Exchange 2013 installation failed to complete, it leaves the Exchange 2013 server object in Active Directory and prevents a new Exchange 2013 installation.

    Hope my clarification is helpful.

    Best regards,
    Amy


    Amy Wang
    TechNet Community Support

    • Marked as answer by cara chen Wednesday, November 20, 2013 9:55 AM
    Monday, November 18, 2013 8:01 AM
  • Amy,

    Thanks for the clarification. I realized that I needed to use ADSI Edit to remove the previous Exchange server object from AD. Had no idea that the setup initialization would have already populated AD without ever getting to the actual installation itself. 

    Thanks again for your help.

    Brandon

    Monday, November 18, 2013 3:37 PM