none
Exchange Server 2007 SP1 installation failed

    Question

  • Hi,

    I'm hoping someone can offer some advice or information re the following issues.

    I'm installing the first Exchange 2007 SP1 server, on Windows Server 2008 x64, in an existing Exchange 2000 organisation.

    I completed all the AD Prep steps successfully and ran Exchange Server 2007 SP1 setup which failed at the Hub Transport stage with the following error . . .

    Log Name:      Application
    Source:        MSExchangeSetup
    Date:          2/20/2009 3:22:33 PM
    Event ID:      1002
    Task Category: Microsoft Exchange Setup
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      **************
    Description:
    Exchange Server component Hub Transport Role failed.
    Error: Error:
    Service 'MSExchangeAntispamUpdate' failed to reach  status 'Running' on this server.

    Cannot start service MSExchangeAntispamUpdate on computer '.'.

    The service did not respond to the start or control request in a timely fashion

    I found TechNet KB944752 which although similar didn't appear to offer a solution for Windows Server 2008.

    I then [probably foolishly] attempted to roll back the installation using Exchange Setup Maintenance Mode which failed to remove the partly installed Hub Transport. Any subsequent attempt to run Exchange setup returns the following error message . . .

    Setup previously failed while performing the action "Uninstall". You cannot resume setup by performing the action "install".

    I've found some similar posts in the forums which mention an issue with IPv6, which was disabled on my target server when I first ran setup. I also re-registered the DiagnosticCmdletController.dll as suggested in KB951183 with no effect.

    So now I'm stuck in the middle with a partially installed Exchange 2007 server which I can't re-install or uninstall. I'm assuming that the original failed installation will already have made configuration changes in the existing Exchange 2000 organisation.

    So before I make things any worse is there a recommended recovery action either to completely remove this failed Exchange Server and start over or re-run and complete the installation ?

    Thanks for any advice anyone can offer.

    Sunday, February 22, 2009 1:24 PM

Answers

  • Please see my post in this thread, try to remove all trace of failed installation

    Then, before we start another installation process, let’s check the Error 1002:

    1.       Please check “Microsoft Exchange Anti-Spam Update” service, see if there's no error info when we try to start the service
    2.       Please check error info in the setup log of first installation under C:\ExchangeSetupLogs

    Services Installed by Exchange Setup

    • Marked as answer by Colin Dalziel Wednesday, March 04, 2009 8:43 PM
    Tuesday, February 24, 2009 4:31 AM

All replies

  • Did the installation manage to create any routing group connectors or server objects for Exchange 2007 server?
    This should be visible in the Exhange System Manager.

    lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
    Sunday, February 22, 2009 6:17 PM
  • Hi Lasse, Thanks for the reply.

    In our legacy Exchange 2000 System manager there is a Routing Group Connector named in the style of <Exchange2000_Server-Exchange2007_Server> in the legacy Administrative Groups but it does not have a target listed in the <Remote Bridgeheads> tab.

    An <Exchange Administrative Group> has also been created with the new Exchange 2007 server listed in the <Servers> folder.

    If I use the Exchange 2007 Management Console on the new server the <Microsoft Exchange/Server Configuration/Hub Transport> item states 'Your Exchange organization has no servers with the Hub Transport role installed', as do the <Client Access> & <Mailbox> items.

    Colin





     

    Monday, February 23, 2009 10:00 AM
  • Please see my post in this thread, try to remove all trace of failed installation

    Then, before we start another installation process, let’s check the Error 1002:

    1.       Please check “Microsoft Exchange Anti-Spam Update” service, see if there's no error info when we try to start the service
    2.       Please check error info in the setup log of first installation under C:\ExchangeSetupLogs

    Services Installed by Exchange Setup

    • Marked as answer by Colin Dalziel Wednesday, March 04, 2009 8:43 PM
    Tuesday, February 24, 2009 4:31 AM
  • Hi James-Luo,

    Thanks for the links.

    I'm interested in Jon Bradleys post in your thread which states ''I would format the box myself'. As part of the preparation for Exchange 2007 I prepared two Windows Server 2008 x64 servers with the same configuration. I would be happy to re-format & re-install the OS on the server where the Ex2007 installation has failed but I'm concerned that the configuration changes made in my legacy Exchange 2000 organisation will cause further problems when I try to install  a second server as the Hub Transport/Client Access/Mailbox Bridgehead. Is removing the failed server & replacing it with a new server install a viable option ?

    Regarding Error 1002, this looks like the relevant info from the ExchangeSetup.log  . . .

    [2/20/2009 3:22:33 PM] [2] [ERROR] Unexpected Error
    [2/20/2009 3:22:33 PM] [2] [ERROR] Service 'MSExchangeAntispamUpdate' failed to reach  status 'Running' on this server.
    [2/20/2009 3:22:33 PM] [2] [ERROR] Cannot start service MSExchangeAntispamUpdate on computer '.'.
    [2/20/2009 3:22:33 PM] [2] [ERROR] The service did not respond to the start or control request in a timely fashion
    [2/20/2009 3:22:33 PM] [2] Ending processing.
    [2/20/2009 3:22:33 PM] [1] The following 1 error(s) occurred during task execution:
    [2/20/2009 3:22:33 PM] [1] 0.  ErrorRecord: Service 'MSExchangeAntispamUpdate' failed to reach  status 'Running' on this server.
    [2/20/2009 3:22:33 PM] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeAntispamUpdate' failed to reach  status 'Running' on this server. ---> System.InvalidOperationException: Cannot start service MSExchangeAntispamUpdate on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
       --- End of inner exception stack trace ---
       at System.ServiceProcess.ServiceController.Start(String[] args)
       at Microsoft.Exchange.Configuration.Tasks.ManageServiceBase.StartServiceWorker(ServiceController serviceController, String[] serviceParameters)
       --- End of inner exception stack trace ---
    [2/20/2009 3:22:33 PM] [1] [ERROR] Service 'MSExchangeAntispamUpdate' failed to reach  status 'Running' on this server.
    [2/20/2009 3:22:33 PM] [1] [ERROR] Cannot start service MSExchangeAntispamUpdate on computer '.'.
    [2/20/2009 3:22:33 PM] [1] [ERROR] The service did not respond to the start or control request in a timely fashion
    [2/20/2009 3:22:33 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
    [2/20/2009 3:22:33 PM] [1] Finished executing component tasks.
    [2/20/2009 3:22:33 PM] [1] Ending processing.
    [2/20/2009 3:38:28 PM] [0] End of Setup

    I'm assuming that this error would occur if I attempted to build a second server or re-install the original failed server, so I'll have to find a fix before attempting another Exchange 2007 install.

    Apologies for the overload of questions but I'm proceeding with extreme caution in order to avoid any further mishaps.

    I'd appreciate any further input you are able to provide.

    Thanks

    Tuesday, February 24, 2009 1:02 PM
  • You said that IPv6 has been disabled on the target server, right? Please verify it by using KB 952842

    Please follow Dvaid’s post in this thread to increase the Service Control Manager time-out value to 180000

    The concern you have about configuration change of failed installation, I suggest that you shall see this article, the method in it suits for this issue

    Please also run Dcdiag” and “Netdiag”, see if there’s any further error info

    [dcdiag >dcdiag.txt | netdiag >netdiag.txt]

    Wednesday, February 25, 2009 3:04 AM
  • Hi James-Luo,

    Thanks again for the really helpful links.

    I'm juggling several projects at the moment, so I won't be able to get back to the Exchange 2007 installation until Mon/Tue-2nd/3rd March 2009.

    I'm intending to remove the failed installation from the legacy organisation using ADSIEdit, fix the IPv6 & SCM time-out issues on a fresh-build Windows 2008 x64 server and start over with a new install of Exchange 2007.

    I'll post back with an update on how it all goes.

    Thursday, February 26, 2009 5:39 PM
  •  J OK
    Friday, February 27, 2009 1:04 AM
  •  Hi James-Luo,

    Thanks again for all your assistance.

    I've now successfully completed the installation of my first Exchange 2007 server in my legacy Exchange 2000 Organisation.



    For anyone else experiening similar issues I carried out the following . . .

    Fully disabled IPv6

    Extended the SCM timeout value

    Removed the original failed server installation from AD

    Installed Exchange 2007 on a fresh-build Windows 2008 x64 server

    All the information required to carry this out are in James-Luo's links in this thread.

    James-Luo provided several postings which contributed to this solution so I've marked his first post as the answer.

     

     

    Wednesday, March 04, 2009 8:42 PM
  • Cool! Glad you solved the issue eventually

    Thursday, March 05, 2009 1:00 AM