Solved

Exchange 2010 Server Removal

Posted on 2011-03-07
5
1,988 Views
Last Modified: 2012-06-05
I currently have a single Exchange 2010 server environment and was working on getting a second server installed.  The 2nd server was added into the environment but unfortunatly, bit the dust over night.  

Fortunately, I did not have any mailboxes or anything important residing on the server...yet.  I rebuilt the server on a different piece of hardware and followed Microsoft's guildlines for Exchange recovery using the setup /m:RecoverServer.

However, every time I attempt this recovery, I get stuck in the exact same spot

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator>E:

E:\>cd exgsp1

E:\EXGSP1>setup /m:recoverserver /t:E:\EXGSRVR

Welcome to Microsoft Exchange Server 2010 Unattended Setup

Setup will continue momentarily, unless you press any key and cancel the
installation. By continuing the installation process, you agree to the license
terms of Microsoft Exchange Server 2010.
If you don't accept these license terms, please cancel the installation. To
review the license terms, please go to
http://go.microsoft.com/fwlink/?LinkId=150127&clcid=0x409/

Press any key to cancel setup................
No key presses were detected.  Setup will continue.
Preparing Exchange Setup

    Copying Setup Files                           COMPLETED

The following server roles will be recovered
Languages
Hub Transport Role
Client Access Role
Mailbox Role
Management Tools

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Language Pack Checks                                      COMPLETED
    Hub Transport Role Checks                                 COMPLETED
    Client Access Role Checks                                 COMPLETED
    Mailbox Role Checks                                       COMPLETED

Configuring Microsoft Exchange Server

    Preparing Setup                                           COMPLETED
    Stopping Services                                         COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Languages                                                 COMPLETED
    Hub Transport Server Role                                 FAILED
     The following error was generated when "$error.Clear();
          if ($exsSid -eq $null -or $exsSid -eq "")
          {
          $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainCont
roller
          }
          start-setupservice -ServiceName MSExchangeADTopology -ServiceParameter
s $exsSid,$RoleDomainController
        " was run: "Service 'MSExchangeADTopology' failed to reach status 'Runni
ng' on this server.".


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Exchange Server setup encountered an error.

E:\EXGSP1>


Every time the Hub Transport Server Role gets configured, it halts at 98% when it's trying to start the MS Exchange AD Topology service.

I've gone through the Microsoft articles and followed them exactly but with no luck.
I made sure to reset the computer account, the targetdir is in the correct spot as well.  The server is set up exactly how the old server was.

Since I do not need any data saved from this specific Exchange server, I need to get this server out of EMC.  I can easily just rebuild the server with a different name, but I can't have the old server hanging out in EMC.  

I know you can remove it from EMC via the ADSI Edit tool, but every article I've read regarding this has been too vague.  What EXACTLY do i need to delete out of ADSI Edit.  

Is it just Services->MS Exchange->(Org)->Admin groups->Exg Admin Group->Servers->(Bad Server) ?  or are there other objects I need to remove?
0
Comment
Question by:macdaddy2005
  • 3
5 Comments
 
LVL 11

Expert Comment

by:MichaelVH
ID: 35068232
Just to make sure. Did you reset the broken Exchange servers's computer account and added the replacement with the same account?

Could you post the details of the ExchangeSetuplog please?
0
 

Author Comment

by:macdaddy2005
ID: 35069100
I did reset the broken exchange server computer account and used it for the new server.  Everything works fine up until the point of starting the AD Topology service.  I've rebuilt the new server from scratch 3 times and it always gets stuck at the exact same spot.  Here's the last portion of the ExchangeSetup log.

[03/07/2011 23:21:59.0843] [2] Ending processing configure-WSManIISHosting
[03/07/2011 23:21:59.0843] [1] Processing component 'Active Directory Topology Service Configuration' (Configuring Microsoft Exchange Active Directory Topology service).
[03/07/2011 23:21:59.0843] [1] Executing:
          if ($exsSid -eq $null -or $exsSid -eq "")
          {
          $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController
          }
          start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController
       
[03/07/2011 23:21:59.0843] [2] Active Directory session settings for 'get-ExchangeServerGroupSid' are: View Entire Forest: 'True', Configuration Domain Controller: 'CORP02PDC.cr***********t.org', Preferred Global Catalog: 'CORP02PDC.cr***********t.org', Preferred Domain Controllers: '{ CORP02PDC.cr***********t.org }'
[03/07/2011 23:21:59.0843] [2] Beginning processing get-ExchangeServerGroupSID -DomainController:'CORP02PDC.cr***********t.org'
[03/07/2011 23:21:59.0843] [2] Used domain controller CORP02PDC.cr***********t.org to read object DC=cr***********t,DC=org.
[03/07/2011 23:21:59.0858] [2] Used domain controller CORP02PDC.cr***********t.org to read object CN=Exchange Servers,OU=Microsoft Exchange Security Groups,DC=cr***********t,DC=org.
[03/07/2011 23:21:59.0858] [2] Used domain controller CORP02PDC.cr***********t.org to read object CN=Exchange Servers,OU=Microsoft Exchange Security Groups,DC=cr***********t,DC=org.
[03/07/2011 23:21:59.0858] [2] Ending processing get-ExchangeServerGroupSID
[03/07/2011 23:21:59.0858] [2] Active Directory session settings for 'start-SetupService' are: View Entire Forest: 'True', Configuration Domain Controller: 'CORP02PDC.cr***********t.org', Preferred Global Catalog: 'CORP02PDC.cr***********t.org', Preferred Domain Controllers: '{ CORP02PDC.cr***********t.org }'
[03/07/2011 23:21:59.0858] [2] Beginning processing start-setupservice -ServiceName:'MSExchangeADTopology' -ServiceParameters:'S-1-5-21-282078301-832208336-1539857752-19434','CORP02PDC.cr***********t.org'
[03/07/2011 23:21:59.0905] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.
[03/07/2011 23:21:59.0905] [2] Will wait '30000' milliseconds for the service 'MSExchangeADTopology' to reach status 'Running'.
[03/07/2011 23:22:29.0908] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server after waiting for '30000' milliseconds.
[03/07/2011 23:22:29.0908] [2] Service checkpoint has progressed. Previous checkpoint='1' - Current checkpoint='2'.
[03/07/2011 23:22:29.0908] [2] Will wait '1250000' milliseconds for the service 'MSExchangeADTopology' to reach status 'Running'.
[03/07/2011 23:43:20.0064] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server after waiting for '1250000' milliseconds.
[03/07/2011 23:43:20.0064] [2] Service Control Manager reports no process ID for service MSExchangeADTopology.
[03/07/2011 23:43:20.0080] [2] Unable to get the process ID for service MSExchangeADTopology because another similar process 0 was found
[03/07/2011 23:43:20.0096] [2] Unexpected Error
[03/07/2011 23:43:20.0096] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[03/07/2011 23:43:20.0111] [2] Ending processing start-setupservice
[03/07/2011 23:43:20.0111] [1] The following 1 error(s) occurred during task execution:
[03/07/2011 23:43:20.0111] [1] 0.  ErrorRecord: Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[03/07/2011 23:43:20.0111] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[03/07/2011 23:43:20.0111] [1] The following error was generated when "$error.Clear();
          if ($exsSid -eq $null -or $exsSid -eq "")
          {
          $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController
          }
          start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController
        " was run: "Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.".
[03/07/2011 23:43:20.0111] [1] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[03/07/2011 23:43:20.0111] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___e95681b135f04f6ca85c706536bfbeed Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/07/2011 23:43:20.0111] [1] Setup is stopping now because of one or more critical errors.
[03/07/2011 23:43:20.0111] [1] Finished executing component tasks.
[03/07/2011 23:43:20.0127] [1] Ending processing DisasterRecovery-BridgeheadRole
[03/07/2011 23:43:20.0143] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[03/07/2011 23:43:20.0158] [0] End of Setup
[03/07/2011 23:43:20.0158] [0] **********************************************



When i watch the services during this portion of the install, the MS AD Topology service is stuck on "Starting" until it finally crashes the setup.
0
 

Accepted Solution

by:
macdaddy2005 earned 0 total points
ID: 35071834
After wasting 8 or so hours, I decided to remove the bad server via ADSI Edit.  I just removed the Server name under "Servers" and removed the Database name under "Databases" and that seems to have worked.  My production EMC no longer shows anything related to that bad server.
0
 

Author Closing Comment

by:macdaddy2005
ID: 35120652
Solved my own issue
0
 

Expert Comment

by:Schmawkins
ID: 38049976
After pounding my head against the wall for several hours with this exact issue, this was the solution that fixed it for me: http://social.technet.microsoft.com/Forums/en/exchange2010/thread/6c1fddf0-b6a5-4f5f-9be0-3bd6d112ab90
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now