Hello,
My environment:
Active Directory – 2 domain controllers on Windows 2016, 2016 Domain level, 2012 R2 Forest Level
Exchange 2013 – 2 serwers. One Front, one mailbox.
We want to migrate to Exchange 2019.
During the installation of new Exchange 2019 CU9 on the new Windows 2019 Server (Full update), we get below error (Event ID 1002 in Windows application logs):
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.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b_91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
There is alsa en error with the ID 4027 in the system logs> Windows Logs> Aplication
Process ExSetupUI.exe (PID=2068). WCF request (Set Config DC DOMAIN.NAIM) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService.
„The connection attempt lasted for a time span of 00:00:02.0468699. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Int32 retry, Boolean& doNotReturnProxyAfterRetry, Boolean useCache)
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
In C:\ExchangeSetupLogs\ExchangeSetup.txt we got
[04.21.2021 10:15:41.0245] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller: 'NTAD01.DOMAIN.NAME', Preferred Global Catalog: 'NTAD01.DOMAIN.NAME', Preferred Domain Controllers: '{ NTAD01.DOMAIN.NAME }'
[04.21.2021 10:15:41.0245] [2] User specified parameters: -DomainController:'NTAD01.DOMAIN.NAME' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[04.21.2021 10:15:41.0245] [2] Beginning processing Set-SharedConfigDC
[04.21.2021 10:15:41.0433] [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 DOMAIN.NAME Site Default-First-Site-Name and connected Sites..
[04.21.2021 10:15:41.0433] [2] No Suitable Directory Servers Found in Forest DOMAIN.NAME Site Default-First-Site-Name and connected Sites.
Additional information:
- IPv6 is enabled on all Exchange serwers and domain controllers.
- We recovered the default domain controller policy because it was modified by a previous IT employee
- we have verified DNS configuration, it looks ok. Domain controllers have correct entries, nslookup replies with correct addresses.
- we deleted usused site in AD Site and Services.
- no firewall on Exchange and Active Directory (Windows firewall off)
any ideas ?
Regards
Daniel