Urgent - Exchange disaster recovery (installation) problem... 1

[gscheepers]

We had a hardware failure on our exchange server and while installing Exchange 2003 it fails on the Messaging and Collaberation Services towards completion with the following error(s):

I'm really struggling to find a resolution and any assistance would be great!

Many thanks in advance!

Gerhard

Error(s):

[10:37:16] Beginning Install of Administrative Group sub-component
[10:37:16] Entering CBaseAtom::FOKToRemoveSharedAtom
[10:37:16] Leaving CBaseAtom::FOKToRemoveSharedAtom
[10:37:16] Entering CBaseServiceAtom(Administrative Group)::ScRemove
[10:37:16] Entering CBaseServiceAtom(Administrative Group)::ScStopAtomServices
[10:37:16] Leaving CBaseServiceAtom(Administrative Group)::ScStopAtomServices
[10:37:16] Entering CBaseAtom(Administrative Group)::ScRemove
[10:37:16] Entering CBaseAtom(Administrative Group)::ScRemoveRegistryKeys
[10:37:16] Removing registry entries for Administrative Group
[10:37:16] Leaving CBaseAtom(Administrative Group)::ScRemoveRegistryKeys
[10:37:16] Removing Active Directory objects for Administrative Group
[10:37:16] Entering CBaseAtom(Administrative Group)::ScRemoveShortcuts
[10:37:16] Leaving CBaseAtom(Administrative Group)::ScRemoveShortcuts
[10:37:16] Removing IIS Metabase objects for Administrative Group
[10:37:16] Leaving CBaseAtom(Administrative Group)::ScRemove
[10:37:16] Entering CBaseServiceAtom(Administrative Group)::ScDeleteAtomServices
[10:37:16] Leaving CBaseServiceAtom(Administrative Group)::ScDeleteAtomServices
[10:37:16] Leaving CBaseServiceAtom(Administrative Group)::ScRemove
[10:37:16] Leaving CAtomAdminGroup::ScAddDSObjects
[10:37:16] Creating Active Directory objects for Administrative Group
[10:37:16] Entering CAtomAdminGroup::ScAdminGroupExists
[10:37:16] Leaving CAtomAdminGroup::ScAdminGroupExists
[10:37:16] Creating administrative group
[10:37:16] Entering ScCreateOrgLevelAdminGroupObject
[10:37:16] Entering CAtomOrgCtChildren::ScSetDefaultAdminACL
[10:37:16] CControlAccessRightObject::ScLookupGuid (f:\titanium\admin\src\libs\logic\security2.cxx:1496)
Error code 0XC0072030 (8240): There is no such object on the server.
[10:37:16] CControlAccessRightObject::ScInitArray (f:\titanium\admin\src\libs\logic\security2.cxx:1595)
Error code 0XC0072030 (8240): There is no such object on the server.
[10:37:16] CAtomOrgCtChildren::ScSetDefaultAdminACL (f:\titanium\admin\src\libs\exsetup\exmisc.cxx:2728)
Error code 0XC0072030 (8240): There is no such object on the server.
[10:37:16] Leaving CAtomOrgCtChildren::ScSetDefaultAdminACL
[10:37:16] ScCreateOrgLevelAdminGroupObject (f:\titanium\admin\src\udog\exsetdata\components\sharedatoms\a_ag.cxx:542)
Error code 0XC0072030 (8240): There is no such object on the server.
[10:37:16] Leaving ScCreateOrgLevelAdminGroupObject
[10:37:16] CAtomAdminGroup::ScAddDSObjects (f:\titanium\admin\src\udog\exsetdata\components\sharedatoms\a_ag.cxx:302)
Error code 0XC0072030 (8240): There is no such object on the server.
[10:37:16] Leaving CAtomAdminGroup::ScAddDSObjects
[10:37:16] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:842)
Error code 0XC0072030 (8240): There is no such object on the server.
[10:37:51] >>>>>>>>>> Setup encountered a fatal error during Microsoft Exchange Messaging and Collaboration Services of Install component task. -- ID:62237 -- CBaseComponent::ScSetup (f:\titanium\admin\src\udog\setupbase\basecomp\basecomp.cxx:1401)
Error code 0XC0072030 (8240): There is no such object on the server.

 

[xmsre]

It's looking for an object in AD, the default first administrative group, and can't find it. Use adsiedit or ldp to verify if it exists or not. If it exists, then the issue is connecting to or reading from AD (connectivity or permissions); if it doesn't then the issue is a missing object.


It should be located in the configuration container.

 

[RichardHuang]

Was the old Exchange server a DC? In addition, you must use the same Exchange server name in order to do the disaster recovery installation.

 

[gscheepers]

Manage to find the problem. There was still a remnance of the previous installation in the services container.

Thanks again.