Hi all, let me just preface by saying thank you very much all your time, help, and patience!
So I've gone through the Exchange 2013 deployment guide, have installed all the pre-requisites, and am now trying to install Exchange 2013 CU7 on (2) 2008 R2 Enterprise SP1 servers. Unfortunately it is failing on both of them at the Mailbox Role: Transport Service - 97% with the following error:
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: "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>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
I've seen and heard the suggestions about enabling IPv6 on the servers as well as the Domain Controllers which I've done to no avail. We do not have IPv6 addresses available on our network as we use IPv4 space, but I've heard just having the IPv6 adapter disabled is a lot of times the issue. So the adapters are set to DHCP even though there's no IPv6 address for it to grab. The 2008 R2 servers that I'm trying to install Exchange 2013 on are VMs on ESX. Will the install fail even if it offers to pick up the installation where I left off? Do I need to completely start from scratch? Any help would be wonderful!