Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2013 SP1 installation fails at Transport service 97%

$
0
0

Good afternoon, all!

I'm setting up a new Exchange infrastructure in our company.  The setup I have is very similar to this posting, except that I have double-checked the IPv6 on both domain controllers and the new 2012 R2 server that Exchange will run on. This server is the first in a planned four-server design: two CAS/Mailbox and two Edge Transport servers. We don't use IPv6 internally yet, so all the IPv6 configs point to link local.  The error after Transport service timed out was:

Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }" was run: "Unable to set shared config DC.".


I've checked the ping and DNS resolves, the new server is a domain member.  Here's a section toward the end of the Exchange Installation log:

[09/03/2015 18:21:51.0473] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:21:51.0473] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:21:51.0473] [2] Waiting 30 seconds before attempting again.
[09/03/2015 18:21:51.0473] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0462] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller: 'isc1.iscinternational.net', Preferred Global Catalog: 'isc1.iscinternational.net', Preferred Domain Controllers: '{ isc1.iscinternational.net }'
[09/03/2015 18:22:21.0462] [2] User specified parameters:  -DomainController:'isc1.iscinternational.net' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[09/03/2015 18:22:21.0462] [2] Beginning processing Set-SharedConfigDC
[09/03/2015 18:22:21.0680] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name..
[09/03/2015 18:22:21.0680] [2] No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name.
[09/03/2015 18:22:21.0680] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name..
[09/03/2015 18:22:21.0680] [2] No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name.
[09/03/2015 18:22:21.0680] [2] Ending processing Set-SharedConfigDC
[09/03/2015 18:22:21.0680] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0696] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name..
[09/03/2015 18:22:21.0696] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0696] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0696] [2] Waiting 30 seconds before attempting again.
[09/03/2015 18:22:21.0696] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:51.0690] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:22:51.0690] [2] [ERROR] Unable to set shared config DC.
[09/03/2015 18:22:51.0690] [2] [ERROR] Unable to set shared config DC.
[09/03/2015 18:22:51.0690] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:51.0706] [1] The following 1 error(s) occurred during task execution:
[09/03/2015 18:22:51.0721] [1] 0.  ErrorRecord: Unable to set shared config DC.
[09/03/2015 18:22:51.0721] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[09/03/2015 18:22:51.0753] [1] [ERROR] The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }" was run: "Unable to set shared config DC.".
[09/03/2015 18:22:51.0753] [1] [ERROR] Unable to set shared config DC.
[09/03/2015 18:22:51.0753] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[09/03/2015 18:22:51.0768] [1] Setup is stopping now because of one or more critical errors.
[09/03/2015 18:22:51.0768] [1] Finished executing component tasks.
[09/03/2015 18:22:51.0862] [1] Ending processing Install-BridgeheadRole

I suspect there's a problem with the Site Default-First-Site-Name part - I did specify a new Exchange Organization name during the first part of setup.

One other detail - this is a 2008 R2 domain, and the nearest DC had a problem with the Network Location - it thought the adapter was in the Public zone. I thought this might be the problem and fixed that by disabling/re-enabling the adapter, but that didn't help the Exchange install.  The second DC was probably registering the Exchange information.

Two questions, then: first, can I rescue this installation, or would I be faster or better off killing this server and spinning up a new one (this is on VMware 5.5)?  I would much rather fix this one than start again.  And second, what issues might I encounter as a result of this failed installation?  Will the install wizard pick up the changes to the AD schema?  I'm pretty sure that won't be a problem, but I don't know for certain.

Thanks to all for looking!

Gregg


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>