Validating cluster resource analysis services
Resolution 1: Verify that all nodes are using correct firmware versions and same driver versions.
Issue 2: A node cannot recover cluster disks that have migrated from a failed node on a shared cluster disk with a different drive letter.
Issue: This error is caused by a SCSI shared drive that is not partitioned properly.
Resolution: Re-create a single partition on the shared disk using the following steps: Issue: Because the Microsoft Distributed Transaction Coordinator (MS DTC) is not completely configured in Windows, applications may fail to enlist SQL Server resources in a distributed transaction.
While words can be deceptive, the human body is a terrible liar.
This is where reading body language and using your own effectively, can be extremely useful when communicating with others.
Resolution 2: Disk drive letters for the cluster disks must be the same on both servers.
If you use the /qb switch, the basic UI in each step will be displayed, including error messages.
When you're reading body language, your primary goal is to determine whether or not a person is comfortable in their current situation.
Once you do this, it's a process of using context and other cues—which we'll get into later—to figure out the specifics.
This can be completed without any interruption of service as it does not affect any online cluster resources.
Validation can be run at any time once the Failover Clustering feature has been installed, including before the cluster has been deployed, during cluster creation and while the cluster is running.