- The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003

Clustering Services
  Where to Start
  Backup & Restore
& Configuration 




Troubleshooting Microsoft Clustering Services 

Troubleshooting Guides
Cluster Server Top Issues
An updated list of the most common Cluster Server issues from Microsoft Support.

Failover/Failback Policies on Microsoft Cluster Server 
Microsoft Knowledge Base Q197047 - Article Microsoft Cluster Server (MSCS) has the ability to define a specific node in the cluster as the preferred node that is to own a particular group. If for any reason this node fails or goes offline, you can set the Cluster service to automatic 

How to Troubleshoot Cluster Service Startup Issues
Microsoft Knowledge Base Article: 266274 - Describes basic troubleshooting steps you can use to diagnose Cluster service startup issues. Although this is not a comprehensive list of all the issues that can cause the Cluster service not to start, it does address about 90% of startup issues. 

MSCS Virtual Server Limitations in a Windows 2000 Domain Environment
Microsoft Knowledge Base Article: 235529 - When you integrate the directory service with the Cluster service, nodes in a server cluster running the Cluster service can be either domain controllers or member servers.

Microsoft Distributed Transaction Coordinator (MSDTC) Recovery Techniques in Windows 2000 Cluster Server
Microsoft Knowledge Base Article: 243204 - The Microsoft Distributed Transaction Coordinator (MSDTC) service is installed by default in Windows 2000, and it is not possible to uninstall it by using Add/Remove Programs. This article describes how to recover from a problem with a Distributed Transaction Coordinator Resource in a Windows 2000 cluster. Typically, you encounter this problem when you install a program that uses the DTC Resource. Programs such as Microsoft SQL Server, and Microsoft Message Queue Server (MSMQ) can use DTC when running on MSCS.

The Meaning of State Codes in the Cluster Log 
Microsoft Knowledge Base Article: 286052 - This article discusses the state codes that are displayed in the Cluster.log file. 

Troubleshooting Event ID 9, 11, and 15 on Cluster Servers
Microsoft Knowledge Base Article: 259237 -When you are using Microsoft Cluster Server (MSCS) or the Cluster service in Windows 2000, events 9, 11, and 15 should not appear in the event log in normal operation. A single occurrence of one of these events may not indicate a problem, but repetitive occurrences may warrant investigation. When you are troubleshooting these events, bear in mind that these events are issued by the device driver for the attached storage devices. These events are not caused by or issued from the cluster software. The events may indicate the need to examine or troubleshoot attached storage devices. 

Windows 2000 Support for Clustered Network Shares 
Microsoft Knowledge Base Article: 238137 -  This article describes resource-clustered share name support in Windows 2000.

Known Bugs and Issues

Antivirus Software May Cause Problems with Cluster Services
Microsoft Knowledge Base Article: 250355 - Antivirus software may cause problems with Cluster services, including issues with failing over resources such as physical disks.

Adding Dependency for Resource with Cluster.exe May Generate Error 5007
Microsoft Knowledge Base Article: 281796 - When you attempt to add a dependency for a resource by using the Cluster.exe command-line utility, you may receive the following error message: System error 5007 has occurred (0x0000138f). The cluster resource could not be found.  

A Removed Disk Can Have Its Corresponding Cluster Resource Started
Microsoft Knowledge Base Article: 306640 - After you remove and replace a physical disk of the same geometry from a cluster during run-time (hot swapping), the original physical disk resource may still come online even though the disk signature of the new drive is different. The same behavior occur ifs the disk signature is changed or damaged while the cluster is in service. Although the new disk resource and the new disk appear to be online, they do not function properly, and Cluster Administrator may not fail the resource.

AutoShareServer Setting Cannot Prevent Administrative Shares on Cluster Nodes
Microsoft Knowledge Base Article 328195 - If you try to disable the administrative shares on a Windows 2000-based cluster by changing the following registry values to 0 (zero), the default administrative shares on cluster disks are not disabled:

Cannot Place Swap File on a Windows NT Cluster Shared Disk
Microsoft Knowledge Base Article: 226108 - The swap file for the members of a Microsoft Windows NT cluster cannot be created on a shared disk.

Changing the IP Address of a Cluster Adapter May Result in Failover
Microsoft Knowledge Base Article: 241828 - Changing the IP address and subnet mask for a network adapter that is designated for internal use only may result in the inability of the nodes to communicate. This may manifest itself as an uncontrolled failover. 

Changing Server Status on a Server Cluster Node Affects Security Permissions
Microsoft Knowledge Base Article: 247720 - If you change a member server to a Domain Controller or vice versa after you install the Cluster service, the service may not start and you receive error messages in the system event log. 

Clustering Cannot Determine If a Shared Disk Is Working Properly
Microsoft Knowledge Base Article: 198513 - A drive that is having hardware problems that allow the drive to be seen but no files to be accessed may appear to be online in Cluster Administrator until a program attempts to gain access to the files

Cluster Configure Application Wizard Does Not Recognize Existing IP Addresses
Microsoft Knowledge Base Article: 282006 - If there is a pre-existing IP address resource, but no Network Name resource in a group, when you run the Configure Application Wizard, you receive the following error message: An error occurred attempting to set private properties on the <GroupName>
The Cluster IP Address is already in use. Error ID: 5057 (000013c1)

Cluster Disks May Be Incorrectly Accessible from All Nodes
Microsoft Knowledge Base Article: 275704 - Although a cluster disk is online on one cluster node, other nodes may be able to access the disk at the same time. This may cause fatal disk corruption. The following error messages may be generated: The file or directory X:\$Mft is corrupt and unreadable. Please run the Chkdsk utility  

Cluster Network Role Changes Automatically
Microsoft Knowledge Base Article: 254651 - If you lose network connectivity on both network adapters on a cluster network when the Media Sense feature is enabled, the network role in the server cluster for that network changes to.. 

"Cluster Network /Prop" Displays Addresses Ending with a Zero
Microsoft Knowledge Base Article: 229081 - When you view the network properties of a cluster server in Windows 2000 by using the "cluster net /prop" command or the "cluster network /properties" command, the last octet of the values with the associated name "address" display the number zero instead of the actual last octet of the Internet Protocol (IP) address or host ID. 

Cluster Server DFS Root Resource Does Not Pass Status Check
Microsoft Knowledge Base Article: 232478 - When you are reviewing a system event log on a node in a server cluster, the following error messages may appear even though no resource problems appear in Cluster Administrator: (updated 962000)

Cluster Service Does Not Start on "Joining" Node in Windows 2000 Cluster
Microsoft Knowledge Base Article: 272129 - The Cluster service starts on the first node on a Windows 2000-based cluster, but may not start on a joining node, or a node may not join an existing cluster on the initial installation. The following events may be logged in the system log 

Cluster Service Generates Additional DNS Traffic
Microsoft Knowledge Base Article: 252764 - Network traces or examination of the cluster log may indicate additional DNS traffic.

Clusdisk Hides Disks Without Signatures
Microsoft Knowledge Base Article: 257503 - If clustering is used on Windows 2000 Advanced Server, disks without signatures may not be available. 

Drive Letter Not Visible After Assignment Change or Moving Cluster Disk
Microsoft Knowledge Base Article: 232276 - You may experience one of the following symptoms: When you use the Disk Management snap-in to change a drive letter on your Windows 2000-based server from your remote Terminal Server client computer, the drive letter change may not be immediately visible. - OR - When you view a Cluster Server from a remote Terminal Server client computer and a failover occurs, you may not be able to access the drive letter or a question mark (?) may be displayed over the letter. - OR - When you attempt to create or remove partitions using the Disk Management snap-in and one of the following occurs: The properties of the new partition report 0 bytes, or the label of the new partition as viewed in the drive properties is inaccurate. 

During Cluster Failover Print Queue Monitoring May Stop
Microsoft Knowledge Base Article: 229733 - When a print queue window is open and actively monitoring the queue of a printer that is shared from a virtual server on a Microsoft server cluster, during node failover, the printer queue may generate the following error message: 

Emergency Repair Disk Does Not Create Cluster Configuration Database
Microsoft Knowledge Base Article: 257892 - When you use an emergency repair disk that was created with Rdisk.exe, a backup copy of the cluster configuration database is not created. 

Error Message on Logon to Cluster Server with SQL 7.0 Installed
Microsoft Knowledge Base Article: 248300 - After you run the SQL Server 7.0, Enterprise Edition, Failover Cluster Wizard and successfully cluster the SQL 7.0 virtual server on Windows 2000, users may occasionally receive the following error message when logging on to a cluster server

Error Message: "An Error Occurred Attempting to Set Properties" on Windows 2000 Cluster Administrator
Microsoft Knowledge Base Article: 237901 - When an administrator is running Windows 2000 Cluster Administrator or the command-line utility, Cluster.exe and then creates a file share resource without a connection to the specified path, the following error message is displayed: Title: Cluster Administrator Standard Extension Description: An error occurred attempting to set properties: The system cannot find the path specified. Error ID: 3 (00000003).  

Event Log Replication Entries Fill Windows 2000 Cluster Log 
Microsoft Knowledge Base Article: 320333 - When too much Event Log replication occurs, the Cluster log may fill up with informational entries that are similar to the following entries:

Hisecdc Causes Problems with Cluster Domain Controllers 
Microsoft Knowledge Base Article: 295091 - After you run the Hisecdc template on one of your domain controllers that are also your clustered nodes, you cannot restart the cluster service on either node.

MAC Address Changes for Virtual Server During a Failover with Clustering
Microsoft Knowledge Base Article: 244331 - After a failover from one cluster node to another, users in a different subnet may be unable to connect to the virtual server.  

MSCS/Cluster Does Not Form with Error Messages 170 and 5086
Microsoft Knowledge Base Article: 249194 - If the Cluster service is started simultaneously on both nodes, it may not start on one of the nodes and produce the following error message: C:\>net start clussvc. The Cluster Service service is starting............... The Cluster Service service could not be started  

Microsoft Cluster Server May Not Share Folders Automatically
Microsoft Knowledge Base Article: 257389 - When you use User Manager for Domains to create domain users and you specify that the path for the user home folders be located on the file share resource of your Microsoft Cluster Server (MSCS) that is running Microsoft Windows NT 4.0 Server 

MSMQ 2.0 as a Server Cluster Resource Does Not Come Online
Microsoft Knowledge Base Article: 247585 - The Message Queuing (MSMQ) resource does not come online after being created in a Windows 2000 Server Cluster, and generates the following error message in the Application Event Log: 

Network Adapter Not Available During Cluster Configuration with a Crossover Cable
Microsoft Knowledge Base Article: 242430 - When you are installing the Cluster service on the first node in a server cluster, Setup may not detect the network adapter that is connected with a crossover cable. 

Network Load Balancing Cluster no Longer Responds to Simple Network Management Protocol Requests
Microsoft Knowledge Base Article: 280307 - Under the following conditions, when all hosts in an Network Load Balancing (NLB) cluster are stopped and then started again, the cluster no longer responds to Simple Network Management Protocol (SNMP) requests: 

No Global Groups Are Available Creating File-Share Resource Permissions in Cluster Administrator
Microsoft Knowledge Base Article: 278710 - When you create a new file-share resource in Cluster Administrator and assign access permissions, the following objects are available: Users Domain local groups Universal groups However, no global groups are available, no matter which domain you select. 

NodeID Change in the Registry Cause Access Violation in Clussvc.exe 
Microsoft Knowledge Base Article: 277700 - The following registry entry identifies the cluster node ID: HKLM/System/CurrentControlSet/Services/Clussvc/Parameters/NodeID If the NodeID is inadvertently changed to the other node number (for example, from 1 to 2 or from 2 to 1) either during an upgrade or manually, an access violation is generated when the Cluster service is started

Problems with Cluster Administration Tool When You Have More Than 100 Disks 
Microsoft Knowledge Base Article: 314753 - When you start the Cluster Administration utility (CluAdmin.exe) and more than 100 physical disk drives are attached to the cluster server, the Cluster Administration utility may stop responding (hang), and may then generate an access violation error.

Recovering from an Event ID 1034 on a Server Cluster
Microsoft Knowledge Base Article: 280425 - After you replace a failed hard disk, or change drives (different SCSI ID, or physical location in the rack) for the shared disk resource, the Microsoft Cluster service may not start. Also, the following error message may be generated in the Event Log: Event ID: 1034 Source: ClusDisk Description: The disk associated with cluster disk resource DriveLetter could not be found. The expected signature of the disk was DiskSignature 

Services for Macintosh Not Supported in a Cluster Environment
Microsoft Knowledge Base Article: 243839 - Services for Macintosh (SFM) is not supported when it is installed on a shared cluster array. In Windows NT 4.0, this is because of architectural restraints imposed by AppleTalk. In Windows 2000, SFM is not supported because SFM maintains state information in memory. Specifically, the Macintosh volume index is located in paged pool memory. Using SFM in clustered mode is not supported and may result in data loss (updated 12/29/1999)

Some Cluster Server File Share Resources Are Not Available
Microsoft Knowledge Base Article: 269137 - When you create a file-share resource on a cluster server and try to share subfolders, some subfolders are not shared or the file-share resource may not come online. Additionally, clients cannot connect to some or all of the subfolders on the file share. 

System Error 52 When You Connect to an NLB Cluster Name
Microsoft Knowledge Base Article: 269156 - When you issue a net view \\clustername command or use another NetBIOS connection on a Windows 2000-based Network Load Balancing (NLB) cluster by cluster name, you may receive the following error message: System Error 52 - A duplicate name exists on the network. 

The Cluster Internet Protocol Address May Not Come Online After the Quorum Disk Is Corrupted
Microsoft Knowledge Base Article: 278951 - If your quorum disk is corrupted and you have run the Chkdsk utility to correct these corruption problems, the cluster Internet Protocol (IP - address may not come online. The Cluster service starts, but the cluster is unavailable. 

Unable to Join or to Fail Over the Cluster if Nodes Have Different Subnets
Microsoft Knowledge Base Article: 279119 - When you attempt to add a node to a cluster, you may receive the following error message: Warning: This system is not attached to all defined cluster networks. Then, a dialog box is displayed to configure the network's name, a step which had already been completed on node A. When you try to fail over an Internet Protocol (IP) address resource to an existing node, the IP address may not come online, an Event ID 1069 message is displayed, and then your system returns to the original node. If you open Cluster Administrator, you may observe an additional network connection listed under "Cluster Configuration / Networks". 

Windows 2000 Cluster Service Does Not Publish Clustered Printers in Active Directory
Microsoft Knowledge Base Article: 300896 - The Cluster service supports the clustering of printer resources to provide highly-available printers to users. The Cluster service is not Active Directory aware and because of this, it does not use Kerberos authentication. If the Cluster service is unable to do this, access is not allowed. When clustered printers are published to Active Directory, they may not be registered properly, and because of this, may not be returned on a search (depending on the choices that are made during the Dcpromo.exe process). 

WINS Resource Does Not Come Online After Cluster Failover
Microsoft Knowledge Base Article: 259593 - After a node failover, the WINS resource being used with the Cluster service may not come online. 

XADM: Content Indexing, Free/Busy Publishing Do Not Work on a Clustered Server
Microsoft Knowledge Base Article: 254360 - When you run Exchange 2000 in a cluster environment, content indexing, free-and-busy publishing, link-state propagation, and SMTP client/server authentication may not work because of authentication problems. 

Entire contents
© 1999-2003 and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with The products referenced in this site are provided by parties other than makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.