question

Rickard-4184 avatar image
0 Votes"
Rickard-4184 asked ·

Problems installing Exchange on-prem 2013 CU23

Hello,
We are having problem upgrading our Exchange on-prem 2013 CU15 to Exchange on-prem 2013 CU23.
The problem we are experiencing are in the prepare domain step and results in the follow error log.
Any ideas about what we can do to continue our installation?

01-27-2021 13:40:29.0619] [2] Beginning processing initialize-DomainPermissions
[01-27-2021 19:20:41.0882] [2] [ERROR] Failed to create a connection to any of the servers in the topology provider.
[01-27-2021 19:20:41.0913] [1] The following 1 error(s) occurred during task execution:
[01-27-2021 19:20:41.0913] [1] 0. ErrorRecord: Failed to create a connection to any of the servers in the topology provider.
[01-27-2021 19:20:41.0913] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.ADTransientException: Failed to create a connection to any of the servers in the topology provider.
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, NetworkCredential networkCredential, ADObjectId domain)
at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)
at Microsoft.Exchange.Data.Directory.ADDataSession.InternalFind[TResult](ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects)
at Microsoft.Exchange.Data.Directory.ADDataSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects)
at Microsoft.Exchange.Data.Directory.ADDataSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADForest.FindRootDomain(Boolean readFromDc)
at Microsoft.Exchange.Management.Tasks.SetupTaskBase.ReadRootDomainFromDc(OrganizationId orgId)
at Microsoft.Exchange.Management.Tasks.SetupTaskBase.PrepareSessionsForRootOrg()
at Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalBeginProcessing()
at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b__5()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01-27-2021 19:20:41.0913] [1] [ERROR] The following error was generated when "$error.Clear();
$createTenantRoot = ($RoleIsDatacenter -or $RoleIsPartnerHosted);
$createMsoSyncRoot = $RoleIsDatacenter;

$RoleDatacenterIsManagementForest is set only in Datacenter deployment; interpret its absense as $false

[bool]$isManagementForest = ($RoleDatacenterIsManagementForest -eq $true);

if ($RolePrepareAllDomains)
{
initialize-DomainPermissions -AllDomains:$true -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -IsManagementForest:$isManagementForest;
}
elseif ($RoleDomain -ne $null)
{
initialize-DomainPermissions -Domain $RoleDomain -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -IsManagementForest:$isManagementForest;
}
else
{
initialize-DomainPermissions -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -IsManagementForest:$isManagementForest;
}
" was run: "Microsoft.Exchange.Data.Directory.ADTransientException: Failed to create a connection to any of the servers in the topology provider.
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, NetworkCredential networkCredential, ADObjectId domain)
at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)
at Microsoft.Exchange.Data.Directory.ADDataSession.InternalFind[TResult](ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects)
at Microsoft.Exchange.Data.Directory.ADDataSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects)
at Microsoft.Exchange.Data.Directory.ADDataSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADForest.FindRootDomain(Boolean readFromDc)
at Microsoft.Exchange.Management.Tasks.SetupTaskBase.ReadRootDomainFromDc(OrganizationId orgId)
at Microsoft.Exchange.Management.Tasks.SetupTaskBase.PrepareSessionsForRootOrg()
at Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalBeginProcessing()
at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b_5()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01-27-2021 19:20:41.0913] [1] [ERROR] Failed to create a connection to any of the servers in the topology provider.
[01-27-2021 19:20:41.0913] [1] [ERROR-REFERENCE] Id=DomainGlobalConfig
__27a706ffe123425f9ee60cb02b930e81 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01-27-2021 19:20:41.0913] [1] Setup is stopping now because of one or more critical errors.
[01-27-2021 19:20:41.0913] [1] Finished executing component tasks.
[01-27-2021 19:20:41.0944] [1] Ending processing Install-ExchangeOrganization
[01-27-2021 19:20:41.0944] [0] CurrentResult console.ProcessRunInternal:198: 1
[01-27-2021 19:20:41.0944] [0] CurrentResult launcherbase.maincore:90: 1
[01-27-2021 19:20:41.0944] [0] CurrentResult console.startmain:52: 1
[01-27-2021 19:20:41.0944] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[01-27-2021 19:20:41.0944] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[01-27-2021 19:20:41.0944] [0] CurrentResult main.run:235: 1
[01-27-2021 19:20:41.0944] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[01-27-2021 19:20:41.0944] [0] CurrentResult setupbase.maincore:396: 1
[01-27-2021 19:20:41.0944] [0] End of Setup
[01-27-2021 19:20:41.0944] [0] **

office-exchange-hybrid-itprooffice-exchange-server-ha
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

EricYin-MSFT avatar image
0 Votes"
EricYin-MSFT answered ·

Hi,

Please can you run dcdiag on each of your domain controllers to check that there aren't any AD replication issues/other issues.

Also, please make sure that the Exchange server has registered its name in DNS correctly and check for any events in the application and system log.

What's your .NET Framework version currently?

Possible cause: According to Microsoft Updates Guidance and Upgrade Paths for CU’s & .NET, you might need upgrading your Exchange server to CU20 and .net version to 4.7.1, then upgrade Exchange server to CU22.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.



If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 4 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We ran dcdiag a few days ago and found errors, but those have been sorted out now. Still waiting on our end to retry the installation again since we cleaned it up. Also had a few older DCs left in our DNS, those have also been sorted.
We have tried on different .NET Frameworks, and right now we are on 4.6.2, but we did notice that after we ran the CU23 installation the "prepare AD steps" fails if we take a lower CU.

[02-11-2021 15:29:27.0726] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: The Active Directory organization configuration version (16133) is higher than Setup's version(16130). Therefore, PrepareAD can't be executed. See the Exchange setup log for more information on this error.

Will try the installation again now that dcdiag errors have been sorted,

0 Votes 0 ·

Hi,
It's suggested to run the installation with .NET Frameworks updated to 4.7.2 or 4.8.
Use this command to ensure that the Exchange server is reporting that it's in the correct site. Check that this site has a working DC and GC:

 NLTEST /DSGETDC:contoso.com


0 Votes 0 ·
EricYin-MSFT avatar image EricYin-MSFT EricYin-MSFT ·

I am writing here to confirm with you how the thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


0 Votes 0 ·
Show more comments