The Microsoft Exchange System Attendant service may not come online if the RootVer registry value is invalid on a server that is running Exchange Server 2003 (906154)


The information in this article applies to:

  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

The Microsoft Exchange System Attendant service may not come online on a server that is running Microsoft Exchange Server 2003 in a Microsoft Windows 2000 active/passive cluster. Additionally, events that are similar to the following may be logged in the Application log:
Event Type: Error
Event Source: MSExchangeSA
Event Category:
Event ID: 1031
Description: One of the System Attendant's task is blocked.
Event Type: Error
Event Source: MSExchangeMU
Event Category:
Event ID: 1043
Description: Metabase Update failed to initialize enumerator of virtual server on cluster database. Error code is error 800706b5.
Event Type: Error
Event Source: MSExchangeMU
Event Category:
Event ID: 1042
Description: Metabase Update failed to read the Configuration namespace property from the domain controller. Error code is 80040a01.
Event Type: Error
Event Source: POP3SVC
Event Category:
Event ID: 1036
Description: An error occurred while starting the Microsoft Exchange POP3 Service: server instance number 1 failed to start with error 0x80040a01.
Event Type: Error
Event Source: IMAP4SVC
Event Category:
Event ID: 1036
Description: An error occurred while starting the Microsoft Exchange IMAP4 Service: server instance number 1 failed to start with error 0x80040a01.
Event Type: Error
Event Source: MSExchangeCluster
Event Category:
Event ID: 1019
Description: Exchange System Attendant: Failed to bring this resource online because of timeout.
Event Type: Error
Event Source: MSExchangeCluster
Event Category:
Event ID: 1003
Description: Exchange System Attendant: Failed to bring the resource online.
Event Type: Error
Event Source: MSExchangeCluster
Event Category:
Event ID: 1012
Description: Exchange Information Store Instance: The RPC call to the service to take the resource offline failed.
Additionally, you may experience the following symptoms when this problem occurs:
  • The Microsoft Exchange Information Store service may not start.
  • The store databases may not start.
  • The Post Office Protocol version 3 (POP3) service may not start.
  • The Internet Message Access Protocol version 4rev1 (IMAP4) service may not start.

CAUSE

This problem occurs if the RootVer registry value is invalid.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If the computer is running the Microsoft .NET Framework 1.1, set the RootVer registry value to 1.1.4322.0. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET

  3. Double-click the RootVer value, type 1.1.4322.0 in the Value data box, and then click OK.
  4. Quit Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This problem may also occur in the following scenarios:
  • When you remove Active Directory from the domain controller, the ASPNET security account is removed. Therefore, the metabase update service may not be able to start. Additionally, several events that are mentioned in the "Symptoms" section may be logged in the Application log. To resolve this problem, reinstall Exchange Server 2003.
  • When there is a permissions issue, several events that are mentioned in the "Symptoms" section may be logged in the Application log. To resolve this problem, run the Exchange Server 2003 Setup program by using the /domainprep switch, as in the following example:

    drive:\setup\i386\setup /domainprep

Modification Type:MajorLast Reviewed:9/2/2005
Keywords:kbexchCLUSTER kbprb KB906154 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.