Article ID: 314266 - Last Review: October 28, 2006 - Revision: 7.2 XADM: Exchange 2000 Cluster Does Not Failover with Error 2074 After You Apply Exchange 2000 SP2This article was previously published under Q314266 SYMPTOMS After you apply Exchange 2000 Server Service Pack 2 (SP2)
to an Exchange 2000 cluster, when the administrator tries to failover one or
more of the virtual servers to the node that you upgraded to Exchange 2000 SP2,
the following error messages may be logged in the Application event log:
Event Type: Error Event Source: MSExchangeCluster Event Category: (4) Event ID: 2074 Computer: NODE2 Description: Exchange Information Store Instance - (VIRTUAL SERVER 1): Cluster Service failed the isalive checking for the resource For more information, click http://search.support.microsoft.com/search/?adv=1. Event Type: Error Event Source: MSExchangeCluster Event Category: (4) Event ID: 2086 Computer: NODE2 Description: Exchange IMAP4 Virtual Server Instance - (VIRTUAL SERVER 1): Failed to set the start bit in the metabase in order to start the protocol, check if any process in the system is dead For more information, click http://search.support.microsoft.com/search/?adv=1. Event Type: Error Event Source: MSExchangeCluster Event Category: (4) Event ID: 2065 Computer: NODE2 Description: Exchange IMAP4 Virtual Server Instance - (VIRTUAL SERVER 1): Failed to bring the resource online CAUSE This problem can occur if you configure too many storage
groups (allotted by the particular role). If too many storage groups are
configured, the Exchange 2000 cluster cannot failover properly. Exchange 2000
Server is limited to four storage groups for each server. This is a physical
limitation and applies to each node of a cluster as well. The following table
describes this limitation. Collapse this table
In this table, the maximum number of storage groups are currently limited to four for each Exchange 2000 virtual server for an active/passive cluster and four for the entire cluster for an active/active cluster configuration. WORKAROUND To work around this problem, run Exchange System Manger and
remove one or more of the of the storage groups until the cluster configuration
conforms to the limitations that are described in the "Cause" section of this
article. When you remove storage groups and mailbox stores, you may encounter
the issue that is described in the following Microsoft Knowledge Base article:
279202
(http://support.microsoft.com/kb/279202/
)
You receive a "c1034a7f" error message when you delete a mailbox store
STATUSMicrosoft has confirmed that
this is a problem in Microsoft Exchange 2000 Server.
MORE INFORMATION Exchange System Manger allows you to create more storage
groups than are allotted for the cluster configuration.
Third-party applications can also create storage groups for
database recovery scenarios that exceed the current failover
allotment. For additional information, see the "Storage Group Limitations" section in the following Exchange 2000 Server white paper: Deploying Microsoft Exchange 2000 Server Service Pack 2 Clusters
(http://go.microsoft.com/fwlink/?LinkId=12403)
| Article Translations
|
Back to the top
