I have two virtual
machines on two separate ESX 4 hosts. Each VM is running Server 2008
Enterprise with Failover Clustering installed. SQL 2008 Enterprise is
installed on the cluster. MSDTC and SAP are also installed on the cluster. The
cluster has been validated and I used a VMware document to configure the
VM's correctly. For some reason the cluster service will fail and will
not failover. You can't even restart the service. The node has to be
rebooted.
Event ID 1574
The failover cluster database could
not be unloaded. If restarting the cluster service does not fix the
problem, please restart the machine.
Before that I get these
events leading up to it. They are not in order but I left the
timestamps on them. Any ideas would be greatly appreciated. Thank you.
Log
Name: System
Source: Ntfs
Date: 6/2/2010
9:50:54 AM
Event ID: 137
Task Category: (2)
Level:
Error
Keywords: Classic
User: N/A
Computer:
DB1
Description:
The default transaction resource manager on
volume J: encountered a non-retryable error and could not start. The
data contains the error code.
---
Log Name: System
Source:
volmgr
Date: 6/2/2010 9:51:03 AM
Event ID:
57
Task Category: (2)
Level: Warning
Keywords:
Classic
User: N/A
Computer: DB1
Description:
The
system failed to flush data to the transaction log. Corruption may
occur.
---
Log Name: Application
Source:
Application Error
Date: 6/2/2010 9:50:49 AM
Event ID:
1000
Task Category: (100)
Level: Error
Keywords:
Classic
User: N/A
Computer: DB1
Description:
Faulting
application clussvc.exe, version 6.0.6002.18005, time stamp 0x49e025d2,
faulting module ntdll.dll, version 6.0.6002.18005, time stamp
0x49e0421d, exception code 0xc0000006, fault offset 0x000000000003347e,
process id 0x7a4, application start time 0x01cb01a48c7cb13c.
-
Log
Name: Application
Source: Application Error
Date:
6/2/2010 9:50:49 AM
Event ID: 1005
Task Category: (100)
Level:
Error
Keywords: Classic
User: N/A
Computer:
DB1
Description:
Windows cannot access the file
C:\Windows\Cluster\clussvc.exe for one of the following reasons:
there is a problem with the network connection, the disk that the file
is stored on, or the storage drivers installed on this computer; or the
disk is missing. Windows closed the program Microsoft Failover Cluster
Service because of this error.
Program: Microsoft Failover
Cluster Service
File: C:\Windows\Cluster\clussvc.exe
The
error value is listed in the Additional Data section.
User Action
1.
Open the file again. This situation might be a temporary problem that
corrects itself when the program runs again.
2. If the file still
cannot be accessed and
- It is on the network, your network
administrator should verify that there is not a problem with the network
and that the server can be contacted.
- It is on a removable
disk, for example, a floppy disk or CD-ROM, verify that the disk is
fully inserted into the computer.
3. Check and repair the file system
by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and
then click OK. At the command prompt, type CHKDSK /F, and then press
ENTER.
4. If the problem persists, restore the file from a backup
copy.
5. Determine whether other files on the same disk can be
opened. If not, the disk might be damaged. If it is a hard disk, contact
your administrator or computer hardware vendor for further assistance.
Additional
Data
Error value: 80000011
Disk type: 3
-
Log
Name: System
Source: Microsoft-Windows-Kernel-General
Date:
6/2/2010 9:50:49 AM
Event ID: 6
Task Category: None
Level:
Error
Keywords:
User: SYSTEM
Computer:
DB1
Description:
An I/O operation initiated by the Registry
failed unrecoverably.The Registry could not flush hive (file):
'\??\C:\Windows\Cluster\CLUSDB'.
-
Log Name:
System
Source: Service Control Manager
Date:
6/2/2010 9:50:53 AM
Event ID: 7031
Task Category: None
Level:
Error
Keywords: Classic
User: N/A
Computer:
DB1
Description:
The Cluster Service service terminated
unexpectedly. It has done this 1 time(s). The following corrective
action will be taken in 60000 milliseconds: Restart the service.