Article ID: 283370
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Advanced Server, Limited Edition
This article was previously published under Q283370
SYMPTOMS
If you type the incorrect path for the Root Path to be used for Quorum logging, this can cause the Microsoft Cluster Server (MSCS) to stop responding (hang). The Cluster service generates the following error message when you type a path with invalid characters:
CAUSE
This problem can occur if you use a forward slash (/) character. If you use a forward slash, the Cluster service may stop responding. This occurs because, according to the logic of the operating system, a forward slash is a typing error, and it is supposed to be a back slash (\) character. The Cluster service does not make this assumption; it interprets it truly as a forward slash, and then it stops responding because this is an invalid character.
RESOLUTION
Start the Cluster service with the Quorum logging disabled, and correct the Quorum path designation. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
280353 How to Change Quorum Disk Designation
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
\MSCS\ is the default directory for Quorum logging if you change the directory to the following:
\MSCS/Quorum\
When you make the change in Cluster Administrator, it may accept this path and assume the path of \MSCS\Quorum\. When the Cluster service is started, it may not work at all because it looks for the exact path of \MSCS/Quorum\ and generates the following error message:
This can cause the entire Cluster to stop responding. Use caution when changing the Quorum Root Path because the Cluster service does not interpret invalid characters like the operating system does.
Additional query words: mscs clustering server cluster
Keywords: kbbug kbclustering kbenv kberrmsg kbnofix KB283370