Export (0) Print
Expand All

How to Troubleshoot Single Copy Clusters Issues

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2008-01-22

This topic provides information about how to troubleshoot the following issues for a clustered mailbox server (CMS) in a single copy cluster (SCC):

  • Database does not mount due to incorrect physical disk dependencies.

  • Quorum resource remains offline or is unavailable.

  • After running Setup /ClearLocalCMS and then Setup /RecoverCMS, messages are not being delivered to mailboxes hosted on the CMS.

  • Installation of a single copy cluster fails with error 0xc0070005 or "Access is Denied".

Other general issues such as Windows Kerberos authentication issues can prevent network resources from coming online in a single copy cluster.

To perform the procedures that resolve the specific issues discussed in this topic, the account you use must be delegated the following permissions:

 

To resolve Use these permissions

Incorrect physical disk dependencies

Exchange Organization Administrator role

Quorum offline or unavailable

Membership in the local Administrators group on the node that owns the quorum resource.

Mail is not being delivered following a recovery of a clustered mailbox server

Exchange Server Administrator role for the CMS and membership in the local Administrators group.

Cannot install single copy cluster

Membership in the local Administrators group

For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

 

Issue: Database does not mount due to incorrect physical disk dependencies

Possible Cause   The physical disk storage for the single copy cluster is not configured with its dependencies correctly. Physical disk dependencies must be manually configured after the CMS has been installed. If the dependencies are not correctly configured, the database will not mount after an outage. To avoid disk dependency issues when you deploy single copy clusters, make sure that you have performed the following high-level steps:

  • Shared storage must be correctly configured at the hardware level prior to forming the failover cluster.

  • Physical disk resource dependencies must be correctly configured for each storage group/database instance after the CMS is installed.

Resolution   Configure the physical disk dependencies correctly. For detailed steps to configure physical disk dependencies after a CMS has been installed, see How to Configure Disk Dependencies for a Single Copy Cluster on Windows Server 2003. For detailed steps to configure the physical disk dependencies during CMS installation, see Installing a Single Copy Cluster on Windows Server 2003 or Installing a Single Copy Cluster on Windows Server 2008, depending on the operating system in use.

 

Issue: Quorum resource remains offline or is unavailable

Possible Cause   Possible causes include storage failures, loss of quorum, mis-configuration, and permissions.

Resolution   For information about troubleshooting quorum issues, see Troubleshooting the Quorum Resource in a Server Cluster. See the following resources for additional information about quorum troubleshooting and recovery:

 

Issue: After running Setup /ClearLocalCMS and then Setup /RecoverCMS, messages are not being delivered to mailboxes hosted on the CMS

Possible Causes   The virtual computer object (VCO) for the CMS is disabled. If the nodes hosting the CMS are running Windows Server 2008 and you ran Setup /ClearLocalCMS to clear the configuration data from the original cluster nodes, the VCO will be disabled.

Resolution   Enable the VCO by using Active Directory Users and Computers. Expand the domain, expand Computers, right-click the VCO, and then click Enable Account.

 

Issue: Installation of a single copy cluster fails with error 0xc0070005 or "Access is Denied"

Possible Cause   This issue may occur if a Network Name resource in the cluster has been configured with the intended name for the CMS.

Resolution   To resolve the problem, remove the Network Name resource and run Setup again. Setup will create the necessary resources automatically.

For information about tools that can help you in troubleshooting single copy clusters, see Tools for Troubleshooting Issues with High Availability Deployments.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft