On a domain controller, use Active Directory Users and Computers to confirm that a computer account (computer object) exists with the same name as the Network Name resource, and that the account is enabled. Confirm that the networks in the nodes are enabled, one or more writeable domain controllers are available on the network, and that elements of the network such as hubs, switches, or bridges appear to be functioning. If you do not currently have Event Viewer open, see "Opening Event Viewer and view events related to failover clustering." After reviewing event messages, check the following:Ĭonfirm that the cluster nodes can communicate with one or more domain controllers. You can increase the disk queue length to avoid this situation. This action affects each server that is attached to the SAN. The tape device driver decreases the disk queue length on the SAN. A tape device on a server is attached to the same storage area network (SAN) that the cluster is using.Typically, the following applications use file system filter drivers: Applications that use file system filter drivers are running on the server.For example, the network adapter driver is outdated. Device drivers on the server are outdated.An application or a service causes a deadlock in the Server service.(This is the most common cause of the symptoms.) A slow disk I/O stream causes disk response time to increase.You may experience these symptoms for one or more of the following reasons: This failure causes the Server service to be unable to keep up with the demand for the network work items that the network layer of the I/O stream queues.įor more information about the IsAlive test, click the following article number to view the article in the Microsoft Knowledge Base:ĩ14458 Behavior of the LooksAlive and IsAlive functions for the resources that are included in the Windows Server Clustering component of Windows Server 2003 Usually, the IsAlive test fails because the Cluster service cannot connect to the Server service (Srv.sys).
When the Cluster service (ClusSvc.exe) cannot perform an IsAlive test against the File Share resource, event ID 1055 is logged. Ensure that a domain controller is accessible to this node within the configured domain. Windows Server 2012 Monitoring Cluster ServiceĬluster network name resource encountered an error logging on to the domainĬluster network name resource '%1' encountered an error logging on to the domain. Cluster network name resource error logging on to the domain Rule
0 kommentar(er)
