Quantcast
Channel: Exchange Server 2013 - High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 1985

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

$
0
0

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.


Viewing all articles
Browse latest Browse all 1985

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>