Home / server / Questions / 248644
Accepted
Jeff
Asked: 2011-03-18 08:19:59 +0800 CST

exchange 2010 installation fails on hub transport role

  • 772

im installing exchange 2010 into a/d with an existing 07 installation

  1. im on a 64 bit server
  2. winodows 2008 R2
  3. 8gb ram
  4. All proper subnets are configured in the sties and services
  5. all domains are raised to a server 2008 functionality level.
  6. Logged on as the domain admin (schema admin, enterprise admin, etc.)
  7. Range setup /PrepareSchema, setup /PrepareAD, setup /PrepareDomain, no errors
  8. DCDIAG /A and DCDIAG /E show no errors
  9. All readiness checks passed seccesfully, no problems
  10. Double checked all PREREQS

i have it automatically install roles needed for exchange 2010

i have watched a couple video instructions on the installation and tried to see if im missing anything, everything looks fine.

whenever the exchange 2010 installation reaches the 'hub transport role, it keeps increasing the timeout and then fails to start the service. after it fails, I can start the service manually however.

Here is the LOGGED error:

[03/17/2011 18:18:56.0006] [1] Processing component 'Active Directory Topology Service Configuration' (Configuring Microsoft Exchange Active Directory Topology service).

[03/17/2011 18:18:56.0006] [1] Executing: 
          if ($exsSid -eq $null -or $exsSid -eq "")
          {
          $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController
          }
          start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController


[03/17/2011 18:18:56.0006] [2] Active Directory session settings for 'start-SetupService' are: View Entire Forest: 'True', Configuration Domain Controller: 'WIN2K8DC1.JEWELS.LOCAL', Preferred Global Catalog: 'WIN2K8DC1.JEWELS.LOCAL', Preferred Domain Controllers: '{ WIN2K8DC1.JEWELS.LOCAL }'

[03/17/2011 18:18:56.0006] [2] Beginning processing start-setupservice -ServiceName:'MSExchangeADTopology' -ServiceParameters:'S-1-5-21-2134851818-3285922005-2538191131-3616','WIN2K8DC1.JEWELS.LOCAL'

[03/17/2011 18:18:56.0037] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.

[03/17/2011 18:18:56.0037] [2] Will wait '30000' milliseconds for the service 'MSExchangeADTopology' to reach status 'Running'.

[03/17/2011 18:19:26.0270] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server after waiting for '30000' milliseconds.

[03/17/2011 18:19:26.0270] [2] Service checkpoint has progressed. Previous checkpoint='1' - Current checkpoint='2'.

[03/17/2011 18:19:26.0270] [2] Will wait '1250000' milliseconds for the service 'MSExchangeADTopology' to reach status 'Running'.

[03/17/2011 18:40:16.0425] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server after waiting for '1250000' milliseconds.

[03/17/2011 18:40:16.0425] [2] Service Control Manager reports no process ID for service MSExchangeADTopology.

[03/17/2011 18:40:16.0425] [2] Unable to get the process ID for service MSExchangeADTopology because another similar process 0 was found

[03/17/2011 18:40:16.0425] [2] [ERROR] Unexpected Error

[03/17/2011 18:40:16.0425] [2] [ERROR] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.

[03/17/2011 18:40:16.0425] [2] Ending processing start-setupservice

[03/17/2011 18:40:16.0425] [1] The following 1 error(s) occurred during task execution:

[03/17/2011 18:40:16.0425] [1] 0.  ErrorRecord: Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.

[03/17/2011 18:40:16.0425] [1] 0.  ErrorRecord: 
Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[03/17/2011 18:40:16.0441] [1] [ERROR] 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/17/2011 18:40:16.0441] [1] [ERROR] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.

[03/17/2011 18:40:16.0441] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___e95681b135f04f6ca85c706536bfbeed Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

[03/17/2011 18:40:16.0441] [1] Setup is stopping now because of one or more critical errors.

Help is appreciated :|

exchange-2007 exchange exchange-migration exchange-2010 windows-server-2008-r2

2 Answers

  1. Best Answer

    I've seen this issue twice before with two different causes:

    1. All IPv6 adapters were disabled. Enabling IPV6 on a NIC fixed it.
    2. The server wasn't in the Exchange Domain Servers group

    After making sure both of these are good, you need to delete the Watermark and Action entries in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\Hub Transport and reboot before trying setup again:

    No guarantees that one of these is the answer, but it's a start.

    • 3

  2. I am migrating exchange 2007 to 2016 today. The path was 2007 --> 2010 --> 2016.

    I had the exact same problem, so I compared group membership of 2007 server and 2010 server. I found that 2007 is in "Exchange Enterprise Servers" group but not in "Exchange Domain Servers" group. Furthermore, "Exchange Domain Servers" is member of "Exchange Enterprise Servers" group.

    So adding exchange2010 to "Exchange Domain Servers" group will inherit permission from "Exchange Enterprise Servers" group also. Somehow exchange2007 is not required to be in "Exchange Domain Servers" group, but has been running without any problem for 10 year now.

    • 0