XADM: When You Join an Exchange 2000 Server to a Mixed Site, Exchange 2000 Does Not Install Properly (313601)



The information in this article applies to:

  • Microsoft Exchange 2000 Server
  • Microsoft Exchange Server 5.5

This article was previously published under Q313601

SYMPTOMS

When you join an Exchange 2000 server to a mixed environment (Exchange 2000 and Exchange Server 5.5), Exchange 2000 Setup may not install the Exchange services and the Site Replication Service (SRS), even though the Setup process appears to finish successfully. The Exchange 2000 server seems to be part of the site, but no SRS exists and no service account exists in the properties of the administrative group.

CAUSE

This issue can occur if the Exchange 2000 server experiences a Domain Name System (DNS) resolution issue. If the Exchange 2000 server experiences a Domain Name System (DNS) resolution issue, it can not resolve the other Exchange computers; therefore, the Exchange 2000 server can not resolve the msExchLegacyAccount (Exchange Server 5.5 service account) from the Exchange Server 5.5 computer and cannot properly join the site.

RESOLUTION

To resolve this issue:
  1. Make sure that your DNS resolution problems have been resolved. You can use a hosts file to make sure that the servers can resolve each other by fully qualified domain name (FQDN).
  2. Manually add the Exchange Server 5.5 service account to the administrative group; to do so, you need to use the ADSI Edit snap-in.

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

    To manually add the Exchange Server 5.5 service account to the administrative group:
    1. Start Exchange System Manager, and then locate the Administrative Group object.
    2. Right-click the Administrative Group object, and then click Properties on the shortcut menu. Notice that the Exchange 5.x Service Account box is not populated.
    3. Open the Windows 2000 support tools, and then run ADSI Edit.
    4. Click the Configuration container (CN=Configuration,DC=ServerNane,DC=com), click the Services container (CN=Services), and then click the Microsoft Exchange container (CN=Microsoft Exchange).
    5. Click the organization container (CN=Exchange_organization_name, for example, CN=TEST), click the Administrative Group container (CN=Administrative Groups), and then click the First Administrative Group container (CN=First Administrative Group).

      NOTE: "First Administrative Group" is the default name for the container unless you renamed the administrative group.
    6. Right-click the First Administrative Group container, and then click Properties on the shortcut menu.
    7. Select which properties to view, change it to both.
    8. Click a property to view, and then change it to "msExchLegacyAccount".
    9. For the attribute values under Syntax, use DirectoryString, and for Value(s), use (not set).
    10. In the Edit Attribute box, type the Exchange Server 5.5 service account name, and then click Set.
    11. In Exchange Service Manager, click Refresh to update the display.
    12. Open the Administrative Group properties again. The Exchange 5.x Service Account box is populated.
    13. Type the Exchange Server 5.5 service account password, and then click OK twice to enter the information that is normally obtained during Setup.
    14. Run Setup.exe to install Exchange 2000 again.
If you use this procedure, Exchange 2000 should install properly in the mixed site.

MORE INFORMATION

When you experience problems with Exchange 2000 Setup, refer to the Exchange 2000 Setup Progress.log file that is located in the root of drive C on your Exchange 2000 server.

The following example is a section of the Exchange 2000 Setup Process.log file that indicates the issue that is described in this article. Start at the top of the log file and search down for "Attempting to read the 55 service account," and then look at that section:

Attempting to read the 55 service account and domain from the AG
[19:28:28] Unable to read a value for the legacy domain from the AG
[19:28:28] Unable to read a value for the legacy service account from the AG
[19:28:28] The 55 Service account read from AG (Pure E2k) was (\)
[19:28:28] There was no AG in the AD, or no legacy svc account on the AD - so we will attempt to get the 55 Svc acct from the 55 server
[19:28:28] No 55 server name available.
[19:28:28] No Parent Component specified for this Account in the ctor - defaulting the initial user value to empty string
[19:28:28] About to attempt to read the 55 service account off the AG (Pure E2k)
[19:28:28] Attempting to read the 55 service account and domain from the AG
[19:28:28] Unable to read a value for the legacy domain from the AG
[19:28:28] Unable to read a value for the legacy service account from the AG
[19:28:28] The 55 Service account read from AG (Pure E2k) was (\)
[19:28:28] There was no AG in the AD, or no legacy svc account on the AD - so we will attempt to get the 55 Svc acct from the 55 server
[19:28:28] No 55 server name available.
[19:28:28] No Parent Component specified for this Account in the ctor - defaulting the initial user value to empty string
[19:28:28] We have detected an existing Org, we will attempt to discover if this AG is mixed.
[19:28:28] About to attempt to discover if this AG is mixed.
[19:28:28] Entering ScRandomlyFindA55ServerNameInAG
[19:28:29] ScRandomlyFindA55ServerNameInAG (K:\admin\src\libs\exsetup\exmisc.cxx:2593)
Error code 0XC0072030 (8240): There is no such object on the server.
[19:28:29] Successfully detected that this is a NOT a Mixed AG
[19:28:29] Entering ScDecideIfSRSShouldBeEnabled
[19:28:29] The SRS will not be enabled.
[19:28:29] Leaving ScDecideIfSRSShouldBeEnabled
[19:28:29] Successfully detected that SRS should NOT be enabled
[19:28:29] We have detected that we should NOT show the Account Page UI
[19:28:33] Setting PTAdministratorAccount from custom property to TEST\exchadmin
[19:28:33] Using the MPC for this Exchange SKU - copying to the context.
[19:28:33] Setup configuration information:
[19:28:33] This is a(n) Enterprise version of Microsoft Exchange 2000
[19:28:33] This is not an evaluation copy of Microsoft Exchange 2000; it will not expire
[19:28:33] InstallSourceDir = Uninitialized
[19:28:33] InstallDestDir = C:\Program Files\Exchsrvr
[19:28:33] InetSrvDir = C:\WINNT\System32\inetsrv
[19:28:33] System32Dir = C:\WINNT\System32
[19:28:33] LocalServer = TESTDC01
[19:28:33] SchemaMasterDC = TESTDC01
[19:28:33] DC = TESTDC01
[19:28:33] Domain = test.com
[19:28:33] DomainDN = /dc=com/dc=test
[19:28:33] NetBIOSDomain = TEST
[19:28:33] NT5Site = Default-First-Site-Name
[19:28:33] Org = EXCHANGE
[19:28:33] LegacyOrg = EXCHANGE
[19:28:33] AdminGroup = Pure E2k
[19:28:33] LegacyAdminGroup = Pure E2k
[19:28:33] AdminGroupContainingRoutingGroup = Pure E2k
[19:28:33] RoutingGroup = First Routing Group
[19:28:33] 55ServiceAccountLogin = Uninitialized
[19:28:33] PTAdministratorAccount = TEST\exchadmin
[19:28:33] This is not a clustered machine
[19:28:33] Entering CCompExchangeRoot::ScInitializeExchangeCompWithCtxInfo
[19:28:33] Leaving CCompExchangeRoot::ScInitializeExchangeCompWithCtxInfo
===========================================================

The following example is a section of the Exchange 2000 Setup Progress.log that indicates success after using the procedure that is described in this article:

About to attempt to read the 55 service account off the AG (TEST-BACKBONE)
[16:22:42] Attempting to read the 55 service account and domain from the AG
[16:22:42] The 55 Service account read from AG (TEST-BACKBONE) was (test1\exchange)
[16:22:42] Setting the 55 sevice account on the Account object
[16:22:42] This is the ForestPrep component - and it is set to Reinstall mode
[16:22:42] The page is never shown for this component in this mode
[16:22:42] We have detected that we should NOT show the Account Page UI
[16:22:42] About to attempt to read the 55 service account off the AG (TEST-BACKBONE)
[16:22:42] Attempting to read the 55 service account and domain from the AG
[16:22:42] The 55 Service account read from AG (TEST-BACKBONE) was (test1\exchange)
[16:22:42] Setting the 55 sevice account on the Account object
[16:22:49] Setting PTAdministratorAccount from custom property to TEST\exchadmin
[16:22:49] Using the MPC for this Exchange SKU - copying to the context.
[16:22:49] Setup configuration information:
[16:22:49] This is a(n) Enterprise version of Microsoft Exchange 2000
[16:22:49] This is not an evaluation copy of Microsoft Exchange 2000; it will not expire
[16:22:49] InstallSourceDir = Uninitialized
[16:22:49] InstallDestDir = C:\Program Files\Exchsrvr
[16:22:49] InetSrvDir = C:\WINNT\System32\inetsrv
[16:22:49] System32Dir = C:\WINNT\System32
[16:22:49] LocalServer = TESTDC01
[16:22:49] SchemaMasterDC = TESTDC01
[16:22:49] DC = TESTDC01
[16:22:49] Domain = test.com
[16:22:49] DomainDN = /dc=com/dc=test
[16:22:49] NetBIOSDomain = TEST
[16:22:49] NT5Site = TEST1
[16:22:49] Org = EXCHANGE
[16:22:49] LegacyOrg = EXCHANGE
[16:22:49] AdminGroup = TEST-BACKBONE
[16:22:49] LegacyAdminGroup = TEST-BACKBONE
[16:22:49] AdminGroupContainingRoutingGroup = Uninitialized
[16:22:49] RoutingGroup = Uninitialized
[16:22:49] 55ServiceAccountLogin = Uninitialized
[16:22:49] PTAdministratorAccount = TEST\exchadmin
[16:22:49] This is not a clustered machine
[16:22:49] Entering CCompExchangeRoot::ScInitializeExchangeCompWithCtxInfo
[16:22:49] Leaving CCompExchangeRoot::ScInitializeExchangeCompWithCtxInfong to the context.


Modification Type:MinorLast Reviewed:4/25/2005
Keywords:kbprb KB313601