| Source | ClusSvc |
| Description | Microsoft Cluster Server suffered an unexpected fatal error at line ### of source module %path%. The error code was 1006. |
| Problem | Messages similar to this may occur in the event of a fatal error that may cause the Cluster Service to terminate on the node that experienced the error. |
| Solution | Check the system event log and the cluster diagnostic logfile for additional information. It is possible that the cluster service may restart itself after the error. This event message may indicate serious problems that may be related to hardware or other causes. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server handled an unexpected error at line 528 of source module G:\Nt\Private\Cluster\Resmon\Rmapi.c. The error code was 5007. |
| Problem | Messages similar to this may occur after installation of Microsoft Cluster Server. If the cluster service starts and successfully forms or joins the cluster, they may be ignored. Otherwise, these errors may indicate a corrupt quorum logfile or other problem. |
| Solution | Ignore the error if the cluster appears to be working properly. Otherwise, you may want to try creating a new quorum logfile using the -noquorumlogging or -fixquorum parameters as documented in the Microsoft Cluster Server Administrator's Guide. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server was halted because of a cluster membership or communications error. The error code was 4. |
| Problem | An error may have occurred between communicating cluster nodes that affected cluster membership. This error may occur if nodes lose the ability to communicate with each other. |
| Solution | Check network adapters and connections between nodes. Check the system event log for errors. There may be a network problem preventing reliable communication between cluster nodes. |
| Source | ClusSvc |
| Description | A new node, "ComputerName", has been added to the cluster. |
| Information | The Microsoft Cluster Server Setup program ran on an adjacent computer. The setup process completed, and the node was admitted for cluster membership. No action required. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server could not join an existing cluster and could not form a new cluster. Microsoft Cluster Server has terminated. |
| Problem | The cluster service started and attempted to join a cluster. The node may not be a member of an existing cluster because of eviction by an administrator. After a cluster node has been evicted from the cluster, the cluster software must be removed and reinstalled if you want it to rejoin the cluster. And, because a cluster already exists with the same cluster name, the node could not form a new cluster with the same name. |
| Solution | Remove MSCS from the affected node, and reinstall MSCS on that system if desired. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server is shutting down because the current node is not a member of any cluster. Microsoft Cluster Server must be reinstalled to make this node a member of a cluster. |
| Problem | The cluster service attempted to run but found that it is not a member of an existing cluster. This may be due to eviction by an administrator or incomplete attempt to join a cluster. This error indicates a need to remove and reinstall the cluster software. |
| Solution | Remove MSCS from the affected node, and reinstall MSCS on that server if desired. |
| Source | ClusSvc |
| Description | Cluster Node "ComputerName" has been evicted from the cluster. |
| Information | A cluster administrator evicted the specified node from the cluster. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server did not start because the current version of Windows NT is not correct. Microsoft Cluster Server runs only on Windows NT Server, Enterprise Edition. |
| Information | The cluster node must be running the Enterprise Edition version of Windows NT Server, and must have Service Pack 3 or later installed. This error may occur if you force an upgrade using the installation disks, which effectively removes any service packs installed. |
| Source | ClusSvc |
| Description | No checkpoint record was found in the logfile W:\Mscs\Quolog.log; the checkpoint file is invalid or was deleted. |
| Problem | The Cluster Service experienced difficulty reading data from the quorum logfile. The logfile could be corrupted. |
| Solution | If the Cluster Service fails to start because of this problem, try manually starting the cluster service with the -noquorumlogging parameter. If you need to adjust the quorum disk designation, use the -fixquorum startup parameter when starting the cluster service. Both of these parameters are covered in the MSCS Administrator's Guide. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server failed to obtain a checkpoint from the cluster database for log file W:\Mscs\Quolog.log. |
| Problem | The cluster service experienced difficulty establishing a checkpoint for the quorum logfile. The logfile could be corrupt, or there may be a disk problem. |
| Solution | You may need to use procedures to recover from a corrupt quorum logfile. You may also need to run chkdsk on the volume to ensure against file system corruption. |
| Source | ClusSvc |
| Description | The log file D:\MSCS\Quolog.log was found to be corrupt. An attempt will be made to reset it, or you should use the Cluster Administrator utility to adjust the maximum size. |
| Problem | The quorum logfile for the cluster was found to be corrupt. The system will attempt to resolve the problem. |
| Solution | The system will attempt to resolve this problem. This error may also be an indication that the cluster property for maximum size should be increased through the Quorum tab. You can manually resolve this problem by using the -noquorumlogging parameter. |
| Source | ClusSvc |
| Description | There is insufficient disk space remaining on the quorum device. Please free up some space on the quorum device. If there is no space on the disk for the quorum log files then changes to the cluster registry will be prevented. |
| Problem | Available disk space is low on the quorum disk and must be resolved. |
| Solution | Remove data or unnecessary files from the quorum disk so that sufficient free space exists for the cluster to operate. If necessary, designate another disk with adequate free space as the quorum device. |
| Source | ClusSvc |
| Description | There is insufficient space left on the quorum device. The Microsoft Cluster Server cannot start. |
| Problem | Available disk space is low on the quorum disk and is preventing the startup of the cluster service. |
| Solution | Remove data or unnecessary files from the quorum disk so that sufficient free space exists for the cluster to operate. If necessary, use the -fixquorum startup option to start one node. Bring the quorum resource online and adjust free space or designate another disk with adequate free space as the quorum device. |
| Source | ClusSvc |
| Description | The quorum resource was not found. The Microsoft Cluster Server has terminated. |
| Problem | The device designated as the quorum resource could not be found. This could be due to the device having failed at the hardware level, or that the disk resource corresponding to the quorum drive letter does not match or no longer exists. |
| Solution | Use the -fixquorum startup option for the cluster service. Investigate and resolve the problem with the quorum disk. If necessary, designate another disk as the quorum device and restart the cluster service before starting other nodes. |
| Source | ClusSvc |
| Description | The registry checkpoint for cluster resource "resourcename" could not be restored to registry key registrykeyname. The resource may not function correctly. Make sure that no other processes have open handles to registry keys in this registry subkey. |
| Problem | The registry key checkpoint imposed by the cluster service failed because an application or process has an open handle to the registry key or subkey. |
| Solution | Close any applications that may have an open handle to the registry key so that it may be replicated as configured with the resource properties. If necessary, contact the application vendor about this problem. |
| Source | ClusSvc |
| Description | The disk associated with cluster disk resource resource name could not be found. The expected signature of the disk was signature. If the disk was removed from the cluster, the resource should be deleted. If the disk was replaced, the resource must be deleted and created again to bring the disk online. If the disk has not been removed or replaced, it may be inaccessible at this time because it is reserved by another cluster node. |
| Problem | The cluster service attempted to mount a physical disk resource in the cluster. The cluster disk driver could not locate a disk with this signature. The disk may be offline or may have failed. This error may also occur if the drive has been replaced or reformatted. This error may also occur if another system continues to hold a reservation for the disk. |
| Solution | Determine why the disk is offline or nonoperational. Check cables, termination, and power for the device. If the drive has failed, replace the drive and restore the resource to the same group as the old drive. Remove the old resource. Restore data from a backup and adjust resource dependencies within the group to point to the new disk resource. |
| Source | ClusSvc |
| Description | Cluster disk resource %1 could not be mounted. |
| Problem | The cluster service attempted to mount a disk resource in the cluster and could not complete the operation. This could be due to a file system problem, hardware issue, or drive letter conflict. |
| Solution | Check for drive letter conflicts, evidence of file system issues in the system event log, and for hardware problems. |
| Source | ClusSvc |
| Description | Cluster disk resource "resourcename" did not respond to a SCSI inquiry command. |
| Problem | The disk did not respond to the issued SCSI command. This usually indicates a hardware problem. |
| Solution | Check SCSI bus configuration. Check the configuration of SCSI adapters and devices. This may indicate a misconfigured or failing device. |
| Source | ClusSvc |
| Description | Cluster disk resource %1 has failed a filesystem check. Please check your disk configuration. |
| Problem | The cluster service attempted to mount a disk resource in the cluster. A filesystem check was necessary and failed during the process. |
| Solution | Check cables, termination, and device configuration. If the drive has failed, replace the drive and restore data. This may also indicate a need to reformat the partition and restore data from a current backup. |
| Source | ClusSvc |
| Description | Reservation of cluster disk "Disk W:" has been lost. Please check your system and disk configuration. |
| Problem | The cluster service had exclusive use of the disk, and lost the reservation of the device on the shared SCSI bus. |
| Solution | The disk may have gone offline or failed. Another node may have taken control of the disk, or a SCSI bus reset command was issued on the bus that caused a loss of reservation. |
| Source | ClusSvc |
| Description | Cluster generic service "ServiceName" could not be found. |
| Problem | The cluster service attempted to bring the specified generic service resource online. The service could not be located and could not be managed by the Cluster Service. |
| Solution | Remove the generic service resource if this service is no longer installed. The parameters for the resource may be invalid. Check the generic service resource properties and confirm correct configuration. |
| Source | ClusSvc |
| Description | Cluster generic service "ServiceName" could not be started. |
| Problem | The cluster service attempted to bring the specified generic service resource online. The service could not be started at the operating system level. |
| Solution | Remove the generic service resource if this service is no longer installed. The parameters for the resource may be invalid. Check the generic service resource properties and confirm correct configuration. Check to make sure the service account has not expired, that it has the correct password, and has necessary rights for the service to start. Check the system event log for any related errors. |
| Source | ClusSvc |
| Description | Cluster generic service "resourcename" failed. |
| Problem | The service associated with the mentioned generic service resource failed. |
| Solution | Check the generic service properties and service configuration for errors. Check system and application event logs for errors. |
| Source | ClusSvc |
| Description | The NetBIOS interface for "IP Address" resource has failed. |
| Problem | The network adapter for the specified IP address resource has experienced a failure. As a result, the IP address is either offline, or the group has moved to a surviving node in the cluster. |
| Solution | Check the network adapter and network connection for problems. Resolve the network-related problem. |
| Source | ClusSvc |
| Description | Cluster IP Address resource %1 could not create the required NetBios interface. |
| Problem | The cluster service attempted to initialize an IP Address resource and could not establish a context with NetBios. |
| Solution | This could be a network adapter- or network adapter driver-related issue. Make sure the adapter is using a current driver and the correct driver for the adapter. If this is an embedded adapter, check with the OEM to determine if a specific OEM version of the driver is a requirement. If you already have many IP Address resources defined, make sure you have not reached the NetBios limit of 64 addresses. If you have IP Address resources defined that do not have a need for NetBios affiliation, use the IP Address private property to disable NetBios for the address. This option is available in SP4 and helps to conserve NetBios address slots. |
| Source | ClusSvc |
| Description | Cluster IP address "IP address" could not create the required TCP/IP Interface.. |
| Problem | The cluster service tried to bring an IP address online. The resource properties may specify an invalid network or malfunctioning adapter. This error may occur if you replace a network adapter with a different model and continue to use the old or inappropriate driver. As a result, the IP address resource cannot be bound to the specified network. |
| Solution | Resolve the network adapter problem or change the properties of the IP address resource to reflect the proper network for the resource. |
| Source | ClusSvc |
| Description | Cluster IP Address resource %1 cannot be brought online because the subnet mask parameter is invalid. Please check your network configuration. |
| Problem | The cluster service tried to bring an IP address resource online but could not do so. The subnet mask for the resource is either blank or otherwise invalid. |
| Solution | Correct the subnet mask for the resource. |
| Source | ClusSvc |
| Description | Cluster IP Address resource %1 cannot be brought online because the IP address parameter is invalid. Please check your network configuration. |
| Problem | The cluster service tried to bring an IP address resource online but could not do so. The IP address property contains an invalid value. This may be caused by incorrectly creating the resource through an API or the command line interface. |
| Solution | Correct the IP address properties for the resource. |
| Source | ClusSvc |
| Description | Cluster IP address, "IP address," cannot be brought online because the specified adapter name is invalid. |
| Problem | The cluster service tried to bring an IP address online. The resource properties may specify an invalid network or a malfunctioning adapter. This error may occur if you replace a network adapter with a different model. As a result, the IP address resource cannot be bound to the specified network. |
| Solution | Resolve the network adapter problem or change the properties of the IP address resource to reflect the proper network for the resource. |
| Source | ClusSvc |
| Description | Cluster IP address "IP address" cannot be brought online because the address IP address is already present on the network. Please check your network configuration. |
| Problem | The cluster service tried to bring an IP address online. The address is already in use on the network and cannot be registered. Therefore, the resource cannot be brought online. |
| Solution | Resolve the IP address conflict, or choose another address for the resource. |
| Source | ClusSvc |
| Description | Cluster Network Name resource %1 cannot be brought online because the name %2 is already present on the network. Please check your network configuration. |
| Problem | The cluster service tried to bring a Network Name resource online. The name is already in use on the network and cannot be registered. Therefore, the resource cannot be brought online. |
| Solution | Resolve the conflict, or choose another network name. |
| Source | ClusSvc |
| Description | Cluster Network Name resource "resourcename" cannot be brought online because it does not depend on an IP address resource. Please add an IP address dependency. |
| Problem | The cluster service attempted to bring the network name resource online, and found that a required dependency was missing. |
| Solution | Microsoft Cluster Server requires an IP address dependency for network name resource types. Cluster Administrator presents a pop-up message if you attempt to remove this dependency without specifying another like dependency. To resolve this error, replace the IP address dependency for this resource. Because it is difficult to remove this dependency, Event 1051 may be an indication of problems within the cluster registry. Check other resources for possible dependency problems. |
| Source | ClusSvc |
| Description | Cluster Network Name resource "resourcename" cannot be brought online because the name could not be added to the system. |
| Problem | The cluster service attempted to bring the network name resource online but the attempt failed. |
| Solution | Check the system event log for errors. Check network adapter configuration and operation. Check TCP/IP configuration and name resolution methods. Check WINS servers for possible database problems or invalid static mappings. |
| Source | ClusSvc |
| Description | Cluster File Share "resourcename" cannot be brought online because the share could not be created. |
| Problem | The cluster service attempted to bring the share online, but the attempt to create the share failed. |
| Solution | Make sure the Server service is started and functioning properly. Check the path for the share. Check ownership and permissions on the directory. Check the system event log for details. Also, if diagnostic logging is enabled, check the log for an entry related to this failure. Use the net helpmsg errornumber command with the error code found in the log entry. |
| Source | ClusSvc |
| Description | Cluster File Share %1 could not be found. |
| Problem | The share corresponding to the named File Share resource was deleted using a mechanism other than Cluster Administrator. This may occur if you select the share with Explorer and choose 'Not Shared'. |
| Solution | Delete shares or take them offline via Cluster Administrator or the command line program CLUSTER.EXE. |
| Source | ClusSvc |
| Description | Cluster File Share "sharename" has failed a status check. |
| Problem | The cluster service (through resource monitors) periodically monitors the status of cluster resources. In this case, a file share failed a status check. This could mean that someone attempted to delete the share through Windows NT Explorer or Server Manager, instead of through Cluster Administrator. This event could also indicate a problem with the Server service, or access to the shared directory. |
| Solution | Check the system event log for errors. Check the cluster diagnostic log (if it is enabled) for status codes that may be related to this event. Check the resource properties for proper configuration. Also, make sure the file share has proper dependencies defined for related resources. |
| Source | ClusSvc |
| Description | The cluster database on the local node is in an invalid state. Please start another node before starting this node. |
| Problem | The cluster database on the local node may be in a default state from the installation process and the node has not properly joined with an existing node. |
| Solution | Make sure another node of the same cluster is online first before starting this node. Upon joining with another cluster node, the node will receive an updated copy of the official cluster database and should alleviate this error. |
| Source | ClusSvc |
| Description | The cluster service CLUSDB could not be opened. |
| Problem | The Cluster Service tried to open the CLUSDB registry hive and could not do so. As a result, the cluster service cannot be brought online. |
| Solution | Check the cluster installation directory for the existence of a file called CLUSDB. Make sure the registry file is not held open by any applications, and that permissions on the file allow the cluster service access to this file and directory. |
| Source | ClusSvc |
| Description | The Cluster Resource Monitor could not load the DLL %1 for resource type %2. |
| Problem | The Cluster Service tried to bring a resource online that requires a specific resource DLL for the resource type. The DLL is either missing, corrupt, or an incompatible version. As a result, the resource cannot be brought online. |
| Solution | Check the cluster installation directory for the existence of the named resource DLL. Make sure the DLL exists in the proper directory on both nodes. |
| Source | ClusSvc |
| Description | The Cluster Resource DLL %1 for resource type %2 failed to initialize. |
| Problem | The Cluster Service tried to load the named resource DLL and it failed to initialize. The DLL could be corrupt, or an incompatible version. As a result, the resource cannot be brought online. |
| Solution | Check the cluster installation directory for the existence of the named resource DLL. Make sure the DLL exists in the proper directory on both nodes and is of proper version. If the DLL is clusres.dll, this is the default resource DLL that comes with MSCS. Check to make sure the version/date stamp is equivalent to or has a later date than the version contained in the service pack in use. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server successfully formed a cluster on this node. |
| Information | This informational message indicates that an existing cluster of the same name was not detected on the network, and that this node elected to form the cluster and own access to the quorum disk |
| Source | ClusSvc |
| Description | Microsoft Cluster Server successfully joined the cluster. |
| Information | When the Cluster Service started, it detected an existing cluster on the network and was able to successfully join the cluster. No action needed. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server was successfully stopped. |
| Information | The Cluster Service was stopped manually by the administrator. |
| Source | ClusSvc |
| Description | The quorum resource was changed. The old quorum resource could not be marked as obsolete. If there is a partition in time, you may lose changes to your database, because the node that is down will not be able to get to the new quorum resource. |
| Problem | The administrator changed the quorum disk designation without all cluster nodes present. |
| Solution | When other cluster nodes attempt to join the existing cluster, they may not be able to connect to the quorum disk and may not participate in the cluster, because their configuration indicates a different quorum device. For any nodes that meet this criterion, you may need to use the -fixquorum option to start the Cluster Service on these nodes and make configuration changes. |
| Source | ClusSvc |
| Description | Cluster resource %1 failed to come online. |
| Problem | The cluster service attempted to bring the resource online, but the resource could not reach an online status. The resource may have exhausted the timeout period allotted for the resource to reach an online state. |
| Solution | Check any parameters related to the resource and check the event log for details. |
| Source | ClusSvc |
| Description | Cluster disk resource resourcename is corrupted. Running Chkdsk /F to repair problems. |
| Problem | The Cluster Service detected corruption on the indicated disk resource and started Chkdsk /f on the volume to repair the structure. The Cluster Service will automatically perform this operation, but only for cluster-defined disk resources (not local disks). |
| Solution | Scan the event log for additional errors. The disk corruption could be indicative of other problems. Check related hardware and devices on the shared bus and ensure proper cables and termination. This error may be a symptom of failing hardware or a deteriorating drive. |
| Source | ClusSvc |
| Description | Cluster disk resource %1 has corrupt files. Running Chkdsk /F to repair problems. |
| Problem | The Cluster Service detected corruption on the indicated disk resource and started Chkdsk /f on the volume to repair the structure. The Cluster Service will automatically perform this operation, but only for cluster-defined disk resources (not local disks). |
| Solution | Scan the event log for additional errors. The disk corruption could be indicative of other problems. Check related hardware and devices on the shared bus and ensure proper cables and termination. This error may be a symptom of failing hardware or a deteriorating drive. |
| Source | ClusSvc |
| Description | The cluster file share resource resourcename failed to start. Error 5. |
| Problem | The file share cannot be brought online. The problem may be caused by permissions to the directory or disk in which the directory resides. This may also be related to permission problems within the domain. |
| Solution | Check to make sure that the Cluster Service account has rights to the directory to be shared. Make sure a domain controller is accessible on the network. Make sure dependencies for the share and for other resource in the group are set correctly. Error 5 translates to "Access Denied." |
| Source | ClusSvc |
| Description | Cluster resource "Disk G:" failed. |
| Problem | The named resource failed and the cluster service logged the event. In this example, a disk resource failed. |
| Solution | For disk resources, check the device for proper operation. Check cables, termination, and logfiles on both cluster nodes. For other resources, check resource properties for proper configuration, and check to make sure dependencies are configured correctly. Check the diagnostic log (if it is enabled) for status codes corresponding to the failure. |
| Source | ClusSvc |
| Description | Cluster node attempted to join the cluster but failed with error 5052. |
| Problem | The cluster node attempted to join an existing cluster but was unable to complete the process. This problem may occur if the node was previously evicted from the cluster. |
| Solution | If the node was previously evicted from the cluster, you must remove and reinstall MSCS on the affected server. |
| Source | ClusSvc |
| Description | Cluster node 2 attempted to join but was refused. Error 5052. |
| Problem | Another node attempted to join the cluster and this node refused the request. |
| Solution | If the node was previously evicted from the cluster, you must remove and reinstall MSCS on the affected server. Look in Cluster Administrator to see if the other node is listed as a possible cluster member. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server was halted to prevent an inconsistency within the cluster. The error code was 5028. |
| Problem | The cluster service on the affected node was halted because of some kind of inconsistency between cluster nodes. |
| Solution | Check connectivity between systems. This error may be an indication of configuration or hardware problems. |
| Source | ClusSvc |
| Description | The TCP/IP interface for cluster IP address resourcename has failed. |
| Problem | The IP address resource depends on the proper operation of a specific network interface as configured in the resource properties. The network interface failed. |
| Solution | Check the system event log for errors. Check the network adapter for proper operation and replace the adapter if necessary. Check to make sure the proper adapter driver is loaded for the device and check for newer versions of the driver. |
| Source | ClusSvc |
| Description | The Microsoft Cluster Server could not write file W:\MSCS\Chk7f5.tmp. The disk may be low on disk space, or some other serious condition exists. |
| Problem | The cluster service attempted to create a temporary file in the MSCS directory on the quorum disk. Lack of disk space or other factors prevented successful completion of the operation. |
| Solution | Check the quorum drive for available disk space. The file system may be corrupted or the device may be failing. Check file system permissions to ensure that the cluster service account has full access to the drive and directory. |
| Source | ClusSvc |
| Description | Node %1 is not a member of cluster %2. If the name of the node has changed, Microsoft Cluster Server must be reinstalled. |
| Problem | The cluster service attempted to start but found that it was not a valid member of the cluster. |
| Solution | Microsoft Cluster Server may need to be reinstalled on this node. If this is the result of a server name change, be sure to evict the node from the cluster (from an operational node) prior to reinstallation. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server cannot use network adapter %1 because it does not have a valid IP address assigned to it. |
| Problem | The network configuration for the adapter has changed and the cluster service cannot make use of the adapter for the network that was assigned to it. |
| Solution | Check the network configuration. If a DHCP address was used for the primary address of the adapter, the address may have been lost. For best results, use a static address. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server did not find any network adapters with valid IP addresses installed in the system. The node will not be able to join a cluster. |
| Problem | The network configuration for the system needs to be corrected to match the same connected networks as the other node of the cluster. |
| Solution | Check the network configuration and make sure it agrees with the working node of the cluster. Make sure the same networks are accessible from all systems in the cluster. |
| Source | ClusSvc |
| Description | The node is no longer attached to cluster network network_id by adapter adapter. Microsoft Cluster Server will delete network interface interface from the cluster configuration. |
| Information | The Cluster Service observed a change in network configuration that might be induced by a change of adapter type or by removal of a network. The network will be removed from the list of available networks. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server discovered that the node is now attached to cluster network network_id by adapter adapter. A new cluster network interface will be added to the cluster configuration. |
| Information | The Cluster Service noticed a new network accessible by the cluster nodes, and has added the new network to the list of accessible networks. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server discovered that the node is attached to a new network by adapter adapter. A new network and network interface will be added to the cluster configuration. |
| Information | The cluster service noticed the addition of a new network. The network will be added to list of available networks. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server failed to update the configuration for one of the nodes Network interfaces. The error code was errorcode. |
| Problem | The cluster service attempted to update a cluster node and could not perform the operation. |
| Solution | Use the net helpmsg errorcode command to find an explanation of the underlying error. For example, error 1393 indicates that a corrupted disk caused the operation to fail. |
| Source | ClusSvc |
| Description | Microsoft Cluster Server failed to initialize the RPC services. The error code was %1. |
| Problem | The cluster service attempted to utilize required RPC services and could not successfully perform the operation. |
| Solution | Use the net helpmsg errorcode command to find an explanation of the underlying error. Check the system event log for other RPC related errors or performance problems. |
| Source | ClusSvc |
| Description | Cluster node node name failed to make a connection to the node over network network name. The error code was 1715. |
| Problem | The cluster service attempted to connect to another cluster node over a specific network and could not establish a connection. This error is a warning message. |
| Solution | Check to make sure that the specified network is available and functioning correctly. If the node experiences this problem, it may try other available networks to establish the desired connection. |
| Source | ClusSvc |
| Description | The node was unable to secure its connection to cluster node %1. The error code was %2. Check that both nodes can communicate with their domain controllers. |
| Problem | The cluster service attempted to connect to another cluster node and could not establish a secure connection. This could indicate domain connectivity problems. |
| Solution | Check to make sure that the networks are available and functioning correctly. This may be a symptom of larger network problems or domain security issues. |
| Source | ClusSvc |
| Description | An unrecoverable error caused the join of node nodename to the cluster to be aborted. The error code was errorcode. |
| Problem | A node attempted to join the cluster but was unable to obtain successful membership. |
| Solution | Use the NET HELPMSG errorcode command to obtain further description of the error that prevented the join operation. For example, error code 1393 indicates that a disk structure is corrupted and nonreadable. An error code like this could indicate a corrupted quorum disk. |
| Source | Disk |
| Description | The device \Device\ScsiPort2 did not respond within the timeout period. |
| Problem | An I/O request was sent to a SCSI device and was not serviced within acceptable time. The device timeout was logged by this event. |
| Solution | You may have a device or controller problem. Check SCSI cables, termination, and adapter configuration. Excessive recurrence of this event message may indicate a serious problem that could indicate potential for data loss or corruption. If necessary, contact your hardware vendor for help troubleshooting this problem. |
| Source | W3SVC |
| Description | The server was unable to add the virtual root "/" for the directory "path" because of the following error: The system cannot find the path specified. The data is the error. |
| Problem | The World Wide Web Publishing service could not create a virtual root for the IIS Virtual Root resource. The directory path may have been deleted. |
| Solution | Re-create or restore the directory and contents. Check the resource properties for the IIS Virtual Root resource and ensure that the path is correct. This problem may occur if you had an IIS Virtual Root resource defined and then uninstalled Microsoft Cluster Server without first deleting the resource. In this case, you may evaluate and change virtual root properties by using the Internet Service Manager. |
| Source | DHCP |
| Description | DHCP IP address lease "IP address" for the card with network address "media access control Address" has been denied. |
| Problem | This system uses a DHCP-assigned IP address for a network adapter. The system attempted to renew the leased address and the DHCP server denied the request. The address may already be allocated to another system. The DHCP server may also have a problem. Network connectivity may be affected by this problem. |
| Solution | Resolve the problem by correcting DHCP server problems or assigning a static IP address. For best results within a cluster, use statically assigned IP addresses. |
| Source | DHCP |
| Description | DHCP failed to renew a lease for the card with network address "MAC Address." The following error occurred: The semaphore timeout period has expired. |
| Problem | This system uses a DHCP assigned IP address for a network adapter. The system attempted to renew the leased address and was unable to renew the lease. Network operations on this system may be affected. |
| Solution | There may be a connectivity problem preventing access to the DHCP server that leased the address, or the DHCP server may be offline. For best results within a cluster, use statically assigned IP addresses. |
| Source | Server |
| Description | The server service was unable to recreate the share "Sharename" because the directory "path" no longer exists. |
| Problem | The Server service attempted to create a share using the specified directory path. This problem may occur if you create a share (outside of Cluster Administrator) on a cluster shared device. If the device is not exclusively available to this computer, the server service cannot create the share. Also, the directory may no longer exist or there may be RPC related issues. |
| Solution | Correct the problem by creating a shared resource through Cluster Administrator, or correct the problem with the missing directory. Check dates of RPC files in the system32 directory. Make sure they concur with those contained in the service pack in use, or any hotfixes applied. |
| Source | TCPIP |
| Description | The system detected an address conflict for IP address "IP address" with the system having network hardware address "media access control address." Network operations on this system may be disrupted as a result. |
| Problem | Another system on the network may be using one of the addresses configured on this computer. |
| Solution | Resolve the IP address conflict. Check network adapter configuration and any IP address resources defined within the cluster. |
| Source | Netlogon |
| Description | No Windows NT Domain controller is available for domain "domain." (This event is expected and can be ignored when booting with the "No Net" hardware profile.) The following error occurred: There are currently no logon servers available to service the logon request. |
| Problem | A domain controller for the domain could not be contacted. As a result, proper authentication of accounts could not be completed. This may occur if the network is disconnected or disabled through system configuration. |
| Solution | Resolve the connectivity problem with the domain controller and restart the system. |
| Source | Service Control Manager |
| Description | The Cluster Service failed to start because of the following error: The service did not start because of a logon failure. |
| Problem | The service control manager attempted to start a service (possibly ClusSvc). It could not authenticate the service account. This error may be seen with Event 7013. |
| Solution | The service account could not be authenticated. This may be because of a failure contacting a domain controller, or because account credentials are invalid. Check the service account name and password and ensure that the account is available and that credentials are correct. You may also try running the cluster service from a command prompt (if currently logged on as an administrator) by changing to the %systemroot%\Cluster directory (or where you installed the software) and typing ClusSvc -debug. If the service starts and runs correctly, stop it by pressing CTRL+C and troubleshoot the service account problem. This error may also occur if network connectivity is disabled through the system configuration or hardware profile. Microsoft Cluster Server requires network connectivity. |
| Source | Service Control Manager |
| Description | Logon attempt with current password failed with the following error: There are currently no logon servers available to service the logon request. |
| More Info | The description for this error message may vary somewhat based on the actual error. For example, another error that may be listed in the event detail might be: "Logon Failure: unknown username or bad password." |
| Problem | The service control manager attempted to start a service (possibly ClusSvc). It could not authenticate the service account with a domain controller. |
| Solution | The service account may be in another domain, or this system is not a domain controller. It is acceptable for the node to be a nondomain controller, but the node needs access to a domain controller within the domain as well as the domain that the service account belongs to. Inability to contact the domain controller may occur because of a problem with the server, network, or other factors. This problem is not related to the cluster software and must be resolved before you start the cluster software. This error may also occur if network connectivity is disabled through the system configuration or hardware profile. Microsoft Cluster Server requires network connectivity. |
| Source | Service Control Manager |
| Description | The Cluster Server service terminated with the following error: The quorum log could not be created or mounted successfully |
| Problem | The Cluster Service attempted to start but could not gain access to the quorum log on the quorum disk. This may be because of problems gaining access to the disk or problems joining a cluster that has already formed. |
| Solution | Check the disk and quorum log for problems. If necessary, check the cluster logfile for more information. There may be other events in the system event log that may give more information. |