| Event Id | 2086 |
| Source | MSExchangeCluster |
| Description | Description: 1.Exchange IMAP4 Virtual Server Instance - (RAWN2): Failed to set the start bit in the metabase in order to start the protocol, check if any process in the system is dead 2.Exchange POP3 Virtual Server Instance - (RAWN2): Failed to set the start bit in the metabase in order to start the protocol, check if any process in the system is dead 3.Exchange SMTP Virtual Server Instance - (RAWN2): Failed to set the start bit in the metabase in order to start the protocol, check if any process in the system is dead. |
| Event Information | According to Microsoft: CAUSE 1 : 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. Cluster Type Storage Groups Active/Passive Four storage groups with a maximum of five mailbox stores per storage group for each Exchange 2000 virtual server Active/Active Four storage groups with a maximum of five mailbox stores per storage group for the entire cluster 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 article:Q279202. CAUSE 2: This issue can occur because the following setting in the metabase indicates to the Internet Information Service (IIS) that the corresponding service is cluster enabled: Id: ClusterEnabled If this setting is set to 0 (data==0) and the service is on a cluster, the error messages in the ""Symptoms"" section of this article are logged. RESOLUTION : To resolve this issue, use MetaEdit to change the ""Id: ClusterEnabled"" setting on the cluster nodes that this issue occurs on. WARNING: Using MetaEdit or Mdutil incorrectly can cause serious problems that may r |
| Reference Links | Exchange 2000 Cluster Does Not Failover with Error 2074 After You Apply Exchange 2000 SP2 Q279202:You receive a "c1034a7f" error message when you delete a mailbox store Virtual Server Services Not Started on a Cluster Event 2086 Appears in Event Viewer When You Run Multi-Protocol Services on Windows 2000 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.