Cluster failure and don`t start

Question

Hi.
First, one of cluster node is lost Witness share. After reboot servers cluster service do not started. In Event Viewer write some errors:
Event ID: 1090
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 ID: 7024
The Cluster Service service terminated with service-specific error The system cannot find the file specified..
Event ID: 7031
The Cluster Service service terminated unexpectedly.  It has done this 3 time(s).  The following corrective action will be
taken in 240000 milliseconds: Restart the service.
Please, help my. Say, how i can manualy remove cluster from AD and uninstall feature Failover Cluster from server.
in cluster.log file:
00001e30.00001b60::2010/12/07-15:52:25.371 INFO  -----------------------------+ LOG BEGIN +-----------------------------
00001e30.00001b60::2010/12/07-15:52:25.371 INFO  [CS] Starting clussvc as a service
00001e30.00001b60::2010/12/07-15:52:25.371 INFO  [CS] cluster service logging level is 5
00001e30.00002224::2010/12/07-15:52:25.371 INFO  [CS] Creating cluster node <vector len='1'>
00001e30.00002224::2010/12/07-15:52:25.371 INFO      <item>ClusSvc</item>
00001e30.00002224::2010/12/07-15:52:25.371 INFO  </vector>
00001e30.00000864::2010/12/07-15:52:25.371 INFO  [StartupConfig]: Initializing.
00001e30.00000864::2010/12/07-15:52:25.371 INFO  [StartupConfig]: Local node name: MSK-MAIL1.
00001e30.00000864::2010/12/07-15:52:25.371 ERR   [CS] Service CreateNodeThread Failed, ERROR_FILE_NOT_FOUND(2)' because of 'Open parameters key failed.'
00001e30.00000864::2010/12/07-15:52:25.371 ERR       000007fe:fddaaa7d( ERROR_MOD_NOT_FOUND(126) )
00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:0109f650( ERROR_MOD_NOT_FOUND(126) )
00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:00f1a260( ERROR_MOD_NOT_FOUND(126) )
00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:ff96a368( ERROR_MOD_NOT_FOUND(126) )
00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:0109f5c0( ERROR_MOD_NOT_FOUND(126) )
00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000001:e06d7363( ERROR_MOD_NOT_FOUND(126) )

Answer 1

Sorry to reply to this old thread - just wanted to add a few comments as I've seen this even 1090 in an Exchange 2013 disaster recovery scenario.
Unfortunately in my case we had a 2 node Exchange 2013 DAG where both nodes had lost their cluster configuration and we had this error on both nodes when trying to start the cluster service. Datacenter Activation Coordination (DAC) mode was enabled on the
database and Stop-DatabaseAvailabilityGroup had been run against both AD sites (warning: please note this command actually clears the clusterconfigurations - it's not just a "stop and do nothing" command). The original filesharewitness (third site)
was unavailable. Restore-DatabaseAvailabilityGroup, Start-DatabaseAvailabilityGroup, net start clussvc /forcequorum (/fq) and lots of other tricks failed.
Eventually we had to:
1. Remove database replica from one node
2. Remove the node from the original DAG
3. Create a new DAG on the now "clean" node
4. Mount the database in the new DAG using database portability feature - see:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
This involved:
4a. An ESEUTIL /R E00 command against the old database
4b. Create a new database (used gui)
4c. Set-MailboxDatabase <DatabaseName> -AllowFileRestore $true against new database
4d. Move E00* and *.edb files from old database to new database directory and rename the edb file to its new name
4e. Mount-Database
4f. Get-Mailbox -Database <SourceDatabase> |where {$_.ObjectClass -NotMatch '(SystemAttendantMailbox|ExOleDbSystemMailbox)'}| Set-Mailbox -Database <TargetDatabase>
(at this point the mail service was re-established, Outlook clients started connecting again and queued mail was delivered to mailboxes)
4g. Get-Mailbox -Database <SourceDatabase> -Arbitration | Set-Mailbox -Database <TargetDatabase> -Arbitration
5. Remove the remaining remants of the original database and the original DAG from the second node
6. Join the second node to the new DAG
7. Re-establish database replication
Note: we used the "cluster node /forcecleanup" command and the -ConfigurationOnly switch for some of the powershell commands a few times for the above procedures to work.
Theoretically I would have thought the Restore-DatabaseAvailabilityGroup command should have given a "clean" cluster node (cluster node /forcecleanup) its cluster configuration based on the DAG configuration stored in Active Directoy but it seems
that's not how it works. Creating a new DAG works though so there must be some underlying commands in the Restore-DatabaseAvailabiltyGroup command that requires the cluster configuration to be at least partly present. Luckily creating a new DAG and using the
database portability feature saved the day for us - definitely something I will remember if I'm ever involved in a similar disaster again.