Exchange 2010 MB Server Installation Fails

  • Thread starter Jason Huitt
  • Start date Views 983
Status
Not open for further replies.
J

Jason Huitt



We're trying to get our test environment up to Exchange 2010. We currently have Ex2003 in a child domain, and Exchange 2007 in the root of our test forest. I have already installed the Ex2010 CA/HT roles on a single server, and am attempting to bring up our first Ex2010 mailbox server.

Here are the relavant entires from the ExchangeSetup.log file:

[05/03/2010 20:19:52.0063] [1] Processing component 'Active Directory Topology Service Configuration' (Configuring Microsoft Exchange Active Directory Topology service).
[05/03/2010 20:19:52.0063] [1] Executing 'if ($exsSid -eq $null -or $exsSid -eq "") { $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController } start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController' failed. The error is: False
[05/03/2010 20:19:52.0063] [2] Launching sub-task '$error.Clear(); if ($exsSid -eq $null -or $exsSid -eq "") { $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController } start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController'.
[05/03/2010 20:19:52.0063] [2] Active Directory session settings for 'start-SetupService' are: View Entire Forest: 'True', Configuration Domain Controller: 'TLIMON.csutest.local', Preferred Global Catalog: 'TLIMON.csutest.local', Preferred Domain Controllers: '{ TLIMON.csutest.local }'
[05/03/2010 20:19:52.0063] [2] Runspace context: Executing user: csutest.local/Users/TFJMH, Executing user organization: , Current organization: , RBAC-enabled: Disabled.
[05/03/2010 20:19:52.0063] [2] Beginning processing.
[05/03/2010 20:19:52.0063] [2] Instantiating handler with index 0 for cmdlet extension agent "Admin Audit Log Agent".
[05/03/2010 20:19:52.0063] [2] Current ScopeSet is: {Domain Read Scope: {, }, Domain Write Scope(s): {, }, Configuration Scope: {, }, Server Configuration Scope(s): {, }, , Exclusive Scope: {, }}
[05/03/2010 20:19:52.0063] [2] Resolved current organization: .
[05/03/2010 20:19:52.0454] [2] The maximum wait for the operation is set to '00:15:00'.
[05/03/2010 20:19:52.0454] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[05/03/2010 20:19:52.0454] [2] Previous service status query time is '5/3/2010 2:19:52 PM'.
[05/03/2010 20:19:52.0454] [2] Current service status query time is '5/3/2010 2:19:52 PM'.
[05/03/2010 20:19:52.0454] [2] Will wait '2000' milliseconds for the service 'MSExchangeADTopology' to reach status 'Running'.
[05/03/2010 20:19:54.0485] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server after waiting for '2000' milliseconds.
[05/03/2010 20:19:54.0485] [2] The remaining time for service status change is '00:14:58'.
[05/03/2010 20:19:54.0485] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='2'.
[05/03/2010 20:19:54.0485] [2] Will wait '1250000' milliseconds for the service 'MSExchangeADTopology' to reach status 'Running'.
[05/03/2010 20:40:44.0650] [2] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server after waiting for '1250000' milliseconds.
[05/03/2010 20:40:44.0650] [2] The remaining time for service status change is '-00:05:52'.
[05/03/2010 20:40:44.0650] [2] Service Control Manager reports no process ID for service MSExchangeADTopology
[05/03/2010 20:40:44.0650] [2] Unable to get process id for service MSExchangeADTopology because another similar process 0 was found
[05/03/2010 20:40:44.0650] [2] [ERROR] Unexpected Error
[05/03/2010 20:40:44.0650] [2] [ERROR] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[05/03/2010 20:40:44.0650] [2] Ending processing.
[05/03/2010 20:40:44.0650] [1] The following 1 error(s) occurred during task execution:
[05/03/2010 20:40:44.0650] [1] 0. ErrorRecord: Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[05/03/2010 20:40:44.0650] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[05/03/2010 20:40:44.0681] [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.".
[05/03/2010 20:40:44.0681] [1] [ERROR] Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
[05/03/2010 20:40:44.0681] [1] [WARNING] <<< Setup failed to execute a task. Dumping all variables.... >>>

When this condition manifests itself, I can see that the MSExchangeADTopology service appears to be "Starting", but never changes to "Started". I can confirm that IPv6 is enabled on all the DCs as well as the Exchange servers. I also get warnings from the Exchange Pre-Deployment Analyzer about the Recipient Update Service not being available, however we're pretty certain this is an artifact of Exchange 2003 being in the mix, and we consider that a red herring (given that we've also seen that warning when we did the Exchange 2007 installation).

Got any ideas? When I search for specific text from the setup log file, I don't get many hits... Thanks in advance.

- Jason
 
J

Jon-Alfred Smith



I can confirm that IPv6 is enabled on all the DCs as well as the Exchange servers.

Have you tried to give IPv6 actual addresses, such as:

IPv6 address ::ffff:10.0.0.4
Subnet prefix length 64
Default gateway ::ffff:10.0.0.138
Preferred DNS Server ::1

Have you tried to disable IPv6 on your DCs/GCs?

MCTS: Messaging | MCSE: S+M | Small Business Specialist
 
J

Jason Huitt



It turns out that IPv6 wasn't completely enabled after all - we had a home-grown GPO applying to DCs and member servers which previously disabled IPv6. However instead of altering the GPO to enable IPv6, the link to the GPO was deleted on both the Domain Controllers OU and the OU where the member Exchange servers were located. This had the side effect of not properly clearing the Registry setting which disabled IPv6, and thus it appeared that some DCs had IPv6 enabled and other did not.

Removing the offending Registry setting such that IPv6 connectivity was enabled on all DCs as well as the MB servers fixed the problem, and Exchange 2010 was finally able to install without error.

It's unfortunate that Exchange 2010 installers have a dependency on IPv6, as we definitely aren't ready to proceed with IPv6 in production.
 
Status
Not open for further replies.
Top