locked
Exchange 2013 : Local HA - DAG / Event ID 1090 FailOver Clustering RRS feed

  • Question

  • Hello everybody,

    I have a problem with Exchange 2013.

    I have the following topology:

    • 01 site
    • 04 Exchange Server (02 CAS / 02 MBX)
    • 04 databases all active in MBX01

    I just created the DAG and add the MBX01 server without problem. Then i added the MBX02 server successfully. Then when i validate the services the Cluster Service in MBX02 appear disabled and can't start.

    When i try the service, respond with the following error:

    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          01/12/2016 07:03:33 p.m.
    Event ID:      1090
    Task Category: Startup/Shutdown
    Level:         Critical
    Keywords:     
    User:          SYSTEM
    Computer:      MBX02.DOMINIO.LOCAL
    Description:
    The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '2'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1090</EventID>
        <Version>0</Version>
        <Level>1</Level>
        <Task>8</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2016-12-02T00:03:33.019254000Z" />
        <EventRecordID>5520</EventRecordID>
        <Correlation />
        <Execution ProcessID="7416" ThreadID="2300" />
        <Channel>System</Channel>
        <Computer>MBX02.DOMINIO.LOCAL</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="Status">2</Data>
        <Data Name="NodeName">mbx02</Data>
      </EventData>
    </Event>

    I don't have a backup of the server or system state, this server is new. So i try some steps like:

    • execute Cluster.exe Node EGIEX02 /ForceCleanUp, restart and add the node again.
    • Remove server from DAG and add it again.
    • Remove server from DAG, uninstall failover feature, restart server and add it again to DAG.

    No one Works, any ideas?

    Stay tuned.

    Best regards.

    Friday, December 2, 2016 12:46 AM

Answers

  • Hi Fed,

    Did you run the following command in an elevated command prompt on MBX02 server?

    Cluster.exe Node MBX02 /ForceCleanUp

    Moreover, try opening EMS as administrator also and remove mbx02 from DAG with the following command:

    Remove-DatabaseAvailabilityGroupServer -MailboxServer MBX02 -Identity <DAGName> -ConfigurationOnly
     

    After verify that you've successfully removed the MBX02 server, we can re-add it again to check the result.

    If still not work, I recommend remove/recreate DAG as a test and check if any helps.

    Best Regards,


    Niko Cheng
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Fed Yunis Friday, December 2, 2016 10:48 PM
    • Unmarked as answer by Fed Yunis Friday, December 2, 2016 10:48 PM
    • Marked as answer by Fed Yunis Monday, December 5, 2016 3:30 PM
    Friday, December 2, 2016 10:05 AM

All replies

  • Hi Fed,

    Did you run the following command in an elevated command prompt on MBX02 server?

    Cluster.exe Node MBX02 /ForceCleanUp

    Moreover, try opening EMS as administrator also and remove mbx02 from DAG with the following command:

    Remove-DatabaseAvailabilityGroupServer -MailboxServer MBX02 -Identity <DAGName> -ConfigurationOnly
     

    After verify that you've successfully removed the MBX02 server, we can re-add it again to check the result.

    If still not work, I recommend remove/recreate DAG as a test and check if any helps.

    Best Regards,


    Niko Cheng
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Fed Yunis Friday, December 2, 2016 10:48 PM
    • Unmarked as answer by Fed Yunis Friday, December 2, 2016 10:48 PM
    • Marked as answer by Fed Yunis Monday, December 5, 2016 3:30 PM
    Friday, December 2, 2016 10:05 AM
  • Niko,

    Thanks for your help! all work fine now.

    I had to recreate the DAG with different name.

    Thanks!

    Best Regards.

    Monday, December 5, 2016 3:32 PM