I'm running into an issue with installing an Exchange 2003 server as we migrate from NT4/5.5.The original site is an NT4 domain with an Exchange 5.5 server running on Windows 2000. This is being migrated into a 2003/AD in a new domain. The new domain has been setup and trusts established between the two domains. Additionally I have run ADMT to import users/groups into the new domain. The new DC is replicating DNS information from the old domain. The new DC and old Exchange are both functioning WINS servers. This is the point where I've begun the Exchange installation. I've followed the Exchange 2003 Deploy setup. Dcdiag and netdiag have run fine without any errors (I can post these logs, but they may not be of much help as they'r error-free). Similarly Forestprep and Domainprep ran fine without any errors as well. ADC has been installed and configured on the new Exchange Server (I didn't think this mattered, but does it need to be on the new DC?); it has also passed all replication/verification without errors. This has all been fine up unil Phase3-Step3 of the Exchange Deployment, installing the first Exchange 2003 server.I followed the instructions and have selected to join/update an existing organization. Setup runs until it gets about 40% done, and fails during Microsoft Exchange Forest Preperation. The error window it pops-up is as follows:Setup failed while installing sub-component Exchange Server 2003 - Exchange 5.5 Synchronizer with error code 0xC103798A (please consult the installation logs for a detailed description). You may cancel the installation or try the failed step again.Needless to say, Retrying fails with the same error.Here is what is at the end of the Exchange Setup log:[18:38:07] ***** RETRYING THE FAILED OPERATION *****[18:38:07] Beginning Install of Exchange Server 2003 - Exchange 5.5 Synchronizer sub-component[18:38:07] Entering CAtomPtOz:cAdd[18:38:07] Entering CAtomPtOz:cDecideIfSRSShouldBeEnabled[18:38:07] Entering ScDecideIfSRSShouldBeEnabled[18:38:07] The SRS will be enabled.[18:38:07] Leaving ScDecideIfSRSShouldBeEnabled[18:38:07] Leaving CAtomPtOz:cDecideIfSRSShouldBeEnabled[18:38:07] Entering CBaseServiceAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cAdd[18:38:07] Entering CBaseServiceAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cCreateAtomServices[18:38:07] Leaving CBaseServiceAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cCreateAtomServices[18:38:07] Entering CBaseAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cAdd[18:38:07] Entering CBaseAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cAddRegistryKeys[18:38:07] Configuring registry entries for Exchange Server 2003 - Exchange 5.5 Synchronizer[18:38:07] Leaving CBaseAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cAddRegistryKeys[18:38:07] Creating IIS Metabase objects for Exchange Server 2003 - Exchange 5.5 Synchronizer[18:38:07] Entering CAtomPtOz:cAddDSObjects[18:38:07] Creating Active Directory objects for Exchange Server 2003 - Exchange 5.5 Synchronizer[18:38:07] Copying Active Directory objects from previous version[18:38:07] Entering CAtomPtOz:cCreateCAAndSynchPtWithOzIfNecessary[18:38:07] Creating the connection agreement to enable ADC to join existing sites[18:38:07] Entering ScBuildNewCADN[18:38:07] Built new CA DN of: /dc=local/dc=explore/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=Active Directory Connections/cn=Config CA_explore_EXCHANGE[18:38:07] Leaving ScBuildNewCADN[18:38:07] Entering CAtomPtOz:cCreateCAForADCToEnableJoinOzSite[18:38:07] Entering ScFindHomeADCForCA[18:38:07] The version read for this ADC is (16973842)[18:38:07] Leaving ScFindHomeADCForCA[18:38:07] Entering CAtomPtOz:cCreateNewCADOB[18:38:07] Creating a CA using: /dc=local/dc=explore/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=Active Directory Connections/cn=Config CA_explore_EXCHANGE[18:38:07] Formed the CA DN of: /dc=local/dc=explore/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=Active Directory Connections/cn=Config CA_explore_EXCHANGE[18:38:07] Entering ScGetServerDNSNameFromDS[18:38:07] Leaving ScGetServerDNSNameFromDS[18:38:07] Found FQDN of DC: NEWDC.newdomain.local[18:38:07] Leaving CAtomPtOz:cCreateNewCADOB[18:38:07] Entering CAtomPtOz:cInitSynchronizationPropsOnCA[18:38:07] Entering CAtomPtOz:cReadSchemaMapFromFile[18:38:07] Leaving CAtomPtOz:cReadSchemaMapFromFile[18:38:07] Entering CAtomPtOz:cReadSchemaMapFromFile[18:38:07] Leaving CAtomPtOz:cReadSchemaMapFromFile[18:38:07] Entering ScGetServerDNSNameFromDS[18:38:07] Leaving ScGetServerDNSNameFromDS[18:38:07] Found FQDN of DC: NEWDC.newdomain.local[18:38:16] DS or RPC is busy. Sleep 250 msec.[18:38:23] DS or RPC is busy. Sleep 500 msec.[18:38:31] DS or RPC is busy. Sleep 750 msec.[18:38:40] DS or RPC is busy. Sleep 1730 msec.[18:38:49] DS or RPC is busy. Sleep 1250 msec.[18:38:58] DS or RPC is busy. Sleep 5394 msec.[18:39:11] DS or RPC is busy. Sleep 10124 msec.[18:39:28] DS or RPC is busy. Sleep 11365 msec.[18:39:47] DS or RPC is busy. Sleep 63008 msec.[18:40:58] DSCallHelper::FRetry (f:\titanium\admin\src\libs\base\ds_call.cxx:49) Error code 0XC007054B (1355): The specified domain either does not exist or could not be contacted.[18:40:58] === IGNORING PREVIOUS ERRORS === CAtomPtOz:cInitSynchronizationPropsOnCA, while getting FQDN of 5.5 server (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:1021) The operation has completed successfully.[18:40:58] Couldn't get FQDN of 5.5 server, reverting to NetBIOS: OLDEXCHANGE[18:40:58] Leaving CAtomPtOz:cInitSynchronizationPropsOnCA[18:40:58] Leaving CAtomPtOz:cCreateCAForADCToEnableJoinOzSite[18:40:58] Launching the ADC to synchronize with previous version of Exchange[18:40:58] Entering CAtomPtOz:cLaunchADCToSynchPtWithOzTopology[18:40:58] Executing command "c:\documents and settings\admnacct\desktop\sw_cd_exchange_svr_2003_english_mlf_x09-89786\setup\i386\exchange\adc" -console -RO -CA "cn=Config CA_explore_EXCHANGE,cn=Active Directory Connections,cn=Microsoft Exchange,cn=Services,cn=Configuration,dc=explore,dc=local" -dc NEWDC -log 2 "C:\Active Directory Connector.Log" to synch up Microsoft Exchange Server 2003 with Microsoft Exchange Server 5.5[18:40:58] Process created ... waiting (-1)[18:41:03] Process has exited with 0x80004005[18:41:03] The command "c:\documents and settings\admnacct\desktop\sw_cd_exchange_svr_2003_english_mlf_x09-89786\setup\i386\exchange\adc" -console -RO -CA "cn=Config CA_explore_EXCHANGE,cn=Active Directory Connections,cn=Microsoft Exchange,cn=Services,cn=Configuration,dc=explore,dc=local" -dc NEWDC -log 2 "C:\Active Directory Connector.Log"failed, returning error code -2147467259 (An unknown error has occurred.). -- ID:31136 -- ScCreateProcess (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1821) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] CAtomPtOz:cLaunchADCToSynchPtWithOzTopology (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:467) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] While launching the ADC for synchronization, Setup encountered an error:'Error: 'An internal component has failed.' (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:1134) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] CAtomPtOz:cAddDSObjects(), while calling ScLaunchADCToSynchPtWithOzTopology (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:1135) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] CAtomPtOz:cAddDSObjects (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:276) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] Leaving CAtomPtOz:cAddDSObjects[18:41:03] CBaseAtom:cAdd (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:939) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] Service = '' CBaseServiceAtom:cAdd (f:\titanium\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:210) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] Leaving CBaseServiceAtom(Exchange Server 2003 - Exchange 5.5 Synchronizer):cAdd[18:41:03] CAtomPtOz:cAdd (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:206) Error code 0XC103798A (31114): An internal component has failed.[18:41:03] mode = 'Install' (61953) CAtomPtOz:cSetup (f:\titanium\admin\src\udog\exsetdata\components\server\a_ptoz.cxx:2266) Error code 0XC103798A (31114): An internal component has failed.Any help would be greatly appreciated.

Hi Gordon, Our issue can be caused by the Exchange Server 5.5 site name is changed after the Exchange Server organization is switched to a mixed environment. Therefore, the name of the Exchange Server 5.5 site that is used by the Exchange Server 2003 Setup program differs from the name of the corresponding Admin Group in Active Directory. We can refer to the link below to try to fix our issue. http://support.microsoft.com/kb/907433 Hope it helps.

Elvisw wrote: Hi Gordon, Our issue can be caused by the Exchange Server 5.5 site name is changed after the Exchange Server organization is switched to a mixed environment. Therefore, the name of the Exchange Server 5.5 site that is used by the Exchange Server 2003 Setup program differs from the name of the corresponding Admin Group in Active Directory. We can refer to the link below to try to fix our issue. http://support.microsoft.com/kb/907433 Hope it helps. Sorry, I should have included this information in the first post. When searching for a resolution for this error, I did find this KB article, but the site name in my Exchange 5.5 site appears to already be set correctly. I am definately not as familiar with Exchange 5.5 as with 2003, so it's possible I misread something.This KB states in step 2: "Note the name of the Admin Group that corresponds to the Exchange Server 5.5 site." Where do I find this? I assumed this was just the name of the Exchange 5.5 site, but please correct me if I'm mistaken and it's found elsewhere.Additionally, this article mentions that it differs from the corresponding Adming Group in AD, can I find out what this is set to in AD? I am assuming this can be done with ASDIEdit, but not sure if it will be useful. Thanks again for your help.