Quorum Checkpoint File May Be Corrupted at Shutdown

• Microsoft Windows NT Server, Enterprise Edition version 4.0, used with:
  • Microsoft Cluster Server

SYMPTOMS

When you use Microsoft Cluster Server (MSCS), the Cluster Server service may not be restarted after a shutdown. Any of the following symptoms may occur:

• The cluster database file (located in the %SystemRoot%\Cluster folder) may become corrupted on both nodes (for example, the Clusdb file contains zero bytes on both nodes).



• The quorum_device:\Mscs\Chksequential_number.tmp file may be inconsistent. If it is used by MSCS, it may result in Clusdb corruption.



• The quorum_device:\Mscs\Chksequential_number.tmp file may be outdated, and a checkpoint file may not be written during the interval when the two nodes are up. If the computer's configuration is changed and a recent checkpoint file reflecting this change does not exist, the log files (quorum_device:\Mscs\quolog.log and quorum_device:\Mscs\Chksequential_number.tmp) may contain inconsistent quorum resource information.

CAUSE

When Cluster Server is shutting down, the Cluster Server service tries to create a quorum_device:\Mscs\Chksequential_number.tmp file on the quorum disk. However, it does not check any error status for registry access functions. If it cannot gain access to the registry, the Cluster Server service creates a corrupted file.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/windows/servicepacks/


-or-


• Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

http://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 6.

Additional query words:

Keywords : kbbug4.00 kbfix4.00 NT4SP6Fix
Version : winnt:4.0
Platform : winnt
Issue type : kbbug