Microsoft KB Archive/928436

From BetaArchive Wiki

Article ID: 928436

Article Last Modified on 10/25/2007



APPLIES TO

  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition



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

On a server that is running Microsoft Exchange Server 2003, you may experience one or more of the following symptoms:

  • The Microsoft Exchange System Attendant service does not start.
  • One or more of the following events are logged in the Application log.

    Event ID 1047

    Event Type: Error
    Event Source: MSExchangeMU
    Event Category: General
    Event ID: 1047
    Date: date
    Time: time
    User: N/A
    Computer: ServerName
    Description: Metabase Update failed to properly initialize its context. It will retry initialization every 60 seconds until succeeds or shutdown is requested.

    Event ID: 1031

    Event Type: Error
    Event Source: MSExchangeSA
    Event Category: General
    Event ID: 1031
    Date: date
    Time: time
    User: N/A
    Computer: ServerName
    Description: One of the System Attendant's task is blocked.
    Function: SctartVM Required

  • The Exchange-related virtual directories do not appear in the Microsoft Internet Information Services (IIS) Microsoft Management Console (MMC) snap-in.
  • The DS2MB key does not appear in the metabase.
  • Incoming e-mail messages are rejected. In this scenario, Exchange generates a non-delivery report (NDR) delivery status notification (DSN) message that contains the following information:

    550 No relay allowed.


CAUSE

This problem may occur if one or more of the following conditions are true:

  • The IWAM_COMPUTERNAME account is incorrectly configured.


The Microsoft Exchange System Attendant service has many tasks to perform. One task is the metabase update operation. This operation replicates information from the Active Directory directory service to the IIS metabase. Exchange 2003 uses the IWAM_COMPUTERNAME account to perform this task. Exchange 2003 examines the IWAM_COMPUTERNAME account configuration when the metabase update operation initializes. If the IWAM_COMPUTERNAME account is configured incorrectly, the Microsoft Exchange System Attendant service may not start.


  • More than one Exchange organization is present in Active Directory.
  • An invalid or incorrect value is configured for the following registry entry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\RootVer


RESOLUTION

To resolve this problem, follow these steps.

Step 1: Verify that the IWAM_COMPUTERNAME account is configured correctly

Verify the IWAM_COMPUTERNAME account information. To do this, follow these steps:

  1. Determine which account is configured in the metabase. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, change to the drive:\Inetpub\AdminScripts directory.
    3. Type the following command, and then press ENTER:

      cscript adsutil.vbs get w3svc/wamusername

      Information that resembles the following is returned:

      Microsoft (R) Windows Script Host Version 5.6
      Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
      
      wamusername             : (string) "IWAM_SERVER-1"
  2. Verify that this account is present in the local Security Account Manager (SAM) database if the computer is a member server or that this account is present in Active Directory if the computer is a domain controller.
  3. If this account is not present, you must create it. When you create this account, click to select the Password never expires check box on the General tab of the AccountName Properties dialog box.
  4. Back up the IIS metabase. For more information about how to back up the IIS metabase, click the following article number to view the article in the Microsoft Knowledge Base:

    302573 How to back up and restore IIS

  5. Set the new account name that you created in step 3 in the IIS metabase. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, change to the drive:\Inetpub\AdminScripts directory.
    3. Type the following command, and then press ENTER:

      cscript adsutil.vbs set w3svc/wamusername IWAM_AccountName

  6. Set the password for the account name that you created in step 3 in the IIS metabase. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, change to the drive:\Inetpub\AdminScripts directory.
    3. Type the following command, and then press ENTER:

      cscript adsutil.vbs set w3svc/WAMUserPass password

  7. Verify that the new account information is configured successfully. To do this, run the command that appears in step 1.
  8. Synchronize the IWAM_COMPUTERNAME account information. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, change to the drive:\Inetpub\AdminScripts directory.
    3. Type the following command, and then press ENTER:

      cscript synciwam.vbs -v

      Examine the output from this command to determine whether any errors are returned.
  9. Restart the IIS Admin service.
  10. Start the Exchange-related services.

Note If the cscript synciwam.vbs -v command returns an error result that resembles the following, you can perform additional troubleshooting of this problem:

Output error = Name: IIS Out-Of-Process Pooled Applications 
Key: {3D14228D-FBE1-11D0-995D-00C04FD919C1}

To perform additional troubleshooting, follow these steps:

  1. Click Start, click Run, type dcomcnfg, and then click OK.
  2. In the Component Services Microsoft Management Console (MMC) snap-in, expand Component Services, expand Computers, expand My Computer, and then click COM+ Applications.
  3. In the right pane, right-click the IIS Out-Of-Process Pooled Applications object that has the same GUID as the GUID that appeared in the error results, and then click Properties.
  4. In the IIS Out-Of-Process Pooled Applications Properties dialog box, click the Identity tab.
  5. Verify the account that appears in the User box. If the IWAM_COMPUTERNAME account is a domain account, it should have the format of domain\IWAM_COMPUTERNAME. If this account is a local account, it should have the format of Computername\IWAM_COMPUTERNAME.
  6. After you configure the user account, click OK.
  7. Restart IIS.

If the problem is not resolved, go to "Step 2: Remove incorrect Exchange organizations from Active Directory."

Step 2: Remove incorrect Exchange organizations from Active Directory

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

If the IWAM_COMPUTERNAME account is correct, and if you do not receive any errors when you synchronize the IWAM_COMPUTERNAME account information, determine whether more than one Exchange organization is present in Active Directory. If more than one Exchange organization is present in Active Directory, you must remove the incorrect Exchange organization. To do this, follow these steps:

  1. Start the ADSI Edit tool. To do this, click Start, click Run, type adsiedit.msc, and then click OK.

    Note ADSI Edit is included with the Windows Support Tools. To install the Microsoft Windows 2000 Support Tools, double-click Setup.exe in the Support\Tools folder on the Windows 2000 Server CD. To install the Microsoft Windows Server 2003 Support Tools, double-click SUPTOOLS.MSI in the Support\Tools folder on the Windows Server 2003 CD.
  2. Expand Configuration [domainControllerName.example.com], expand CN=Configuration,DC=example,DC=com, expand CN=Services, and then click CN=Microsoft Exchange.
  3. Examine the containers that appear in the right pane. The following two containers should appear:
    • CN=Active Directory Connections
    • CN=OrganizationName For example, CN=First Organization
    If an invalid Exchange organization also appears in the right pane, you must remove it. To do this, right-click the invalid container, click Delete, and then click Yes to confirm the removal of the container.
  4. Exit the ADSI Edit tool, and then allow for the changes to replicate to the other domain controllers in the organization.
  5. Start the Exchange Setup program, and then run a Reinstall operation of Exchange 2003.

If the problem is not resolved, go to "Step 3: Verify the value of the ASP.NET\RootVer registry entry"

Step 3: Verify the value of the ASP.NET\RootVer registry entry

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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If DS2MB replication does not occur, changes to Exchange components such as recipient policies or SMTP virtual servers are not replicated to the IIS metabase. You may experience this problem if the ASP.NET\RootVer registry entry contains an incorrect value.

If the Microsoft .NET Framework 1.1 is installed, the value of the ASP.NET\RootVer registry entry should be 1.1.4322.0. However, if the Microsoft .NET Framework 1.0 is later installed on the computer, the ASP.NET\RootVer registry entry is changed to also include the hotfix version for the .NET Framework. For example, the ASP.NET\RootVer registry entry value is changed to 1.1.4322.573. In this registry entry, .573 is the hotfix version.

Note For the .NET Framework 1.0, using the full version together with the hotfix version in the registry is the expected behavior. However, this behavior is changed with the .NET Framework 1.1. For the .NET Framework 1.1, the hotfix information is not included in the registry value.

Therefore, if you install the .NET Framework 1.0 after you install the .NET Framework 1.1, the IIS metabase may be unable to access the correct registry path of ASP.NET\1.1.4322.0. Therefore, DS2MB replication is unsuccessful. To resolve this problem, remove the hotfix version information from the ASP.NET\RootVer registry entry. To do this, use one of the following methods:

Method 1: Use Registry Editor to configure the correct value

  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET

  3. In the right pane, right-click RootVer, and then click Modify.
  4. Change the value in the Value data box to remove the hotfix version information. For example, change 1.1.4322.573 to 1.1.4322.0.
  5. Click OK, and then exit Registry Editor.

Method 2: Use ASPNET_REGIIS.EXE to register the correct value

  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, change to the %WINDIR%\Microsoft.NET\Framework\v1.1.4322 directory.
  3. Type the following command, and then press ENTER:

    aspnet_regiis.exe -i

  4. Exit the command prompt.


MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

255770 PRB: Logon failure: Unknown user name or bad password when you run out-of-process webs



Additional query words: XADM MsExchangeMU Metabase DS2MB replication Exchange 2003 Service Pack 1 ASP.NET ASPNET Framework dav2mb

Keywords: kbregistry kbeventlog kbtshoot kbprb KB928436