Произошла следующая ошибка system exception unable to set shared config dc - Ремонт и установка крупной бытовой техники

Remove From My Forums

Question
Hi experts

When trying to install another Exchange 2013 server in my test environment I got the following 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 settingshared config DC. Exception: » + $_.Exception.Message);
}

Write-ExchangeSetupLog -Info («Waiting 30 seconds before attemptingagain.»);
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.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)».

The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.

Did I miss anything? Any solution to this ?

Answers

Hi Hunk8,

Did this error happen when the setup program configuring the mailbox role:transport service and failed?

Are you able to ping the domain controller? Was windows server able to find it?

To Resolve This Issue, Follow The Below Steps.
1. Locate Microsoft.Exchange.Directory.TopologyService.exe.config File , By Default It Should Be Under «C:Program FilesMicrosoftExchange ServerV15Bin»
2. Open NotePad As Administrator & Then Open Microsoft.Exchange.Directory.TopologyService.exe.config File
3. Locate «Topology MinimumPrefixMatch»
4. Add MinSuitableServer = «1»
5. Save The File & Restart Microsoft Exchange Active Directory Topology Services.

Regards,

Beverly Gao

Please remember to
mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
tnsf@microsoft.com.
- Marked as answer by
  
  Thursday, December 19, 2019 2:41 PM

What am I trying to do?

I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:

[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC

[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server ‘TopologyClientTcpEndpoint (localhost)’ returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..

[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.

Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.

What am I running?

2 X DC on domain and forest functional level 2008R2 both writable

1 X fresh install of Windows 2012 R2 which is domain joined

What have I tried?

Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding «Exchange Server» or «Exchange Enterprise Servers» to the group policy and doing the relevant gpupdate /force and reboot :

Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log

Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe

setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms

Making sure the following path has full permissions:

EXCHANGE14:CurrentReleaseSharedDatacenterSetup

Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good

What have I noticed that is suspicious?

Microsoft Exchange Transport service will not start even though both of its dependences services have started:

Microsoft Filtering Management Service

Microsoft Exchange Active Directory Topology Service

It will eventually error with

“Windows could not start the Microsoft Exchange Transport Service on local computer

Error 1053: This Service did not respond to the start of control request in a timely fashion”

This error is from the GUI wizard itself:

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)».

Exchange logs which have been written:

**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??

[01/20/2015 17:13:20.0084] [2] Active Directory session settings for ‘Set-SharedConfigDC’ are: View Entire Forest: ‘True’, Configuration Domain Controller:mydomain.com’, Preferred Global Catalog: ‘mydomain.com’, Preferred Domain Controllers:
‘{ mydomain.com}’

[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com’ -ErrorVariable:’setSharedCDCErrors’ -ErrorAction:’SilentlyContinue’

[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC

[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.

[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC

[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog

[01/20/2015 17:13:20.0193] [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 Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..

[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog

[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog

[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.

[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog

[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog

[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.

[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog

[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:

[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.

[01/20/2015 17:13:50.0288] [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>b__b()

at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)

[01/20/2015 17:13:50.0288] [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: «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)».

[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.

[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:CurrentReleaseSharedDatacenterSetup

[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.

[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.

[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole

Windows Event Viewer:

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn’t find minimal required number of suitable Global Catalog servers
in either the local site ‘Default-First-Site’ or the following sites:

Источник

While installing Exchange 2016 (CU4) in a new customers environment, I encountered an error. The install wizard would fail at 97% on step 6 and there were errors in the setup log file.

I checked the Exchange Setup Log, and tried some troubleshooting based on this information:
Technet article
Technet forum
Reddit

After some digging, I found this error in Event Viewer:

Process ExSetupUI.exe (PID=5772). WCF request (Get Servers for domain.local) 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.0484392. 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 --

Added “Manage audit and security logs” permission for Exchange Servers on the Domain Controllers.
Fixed some issues with missing reverse DNS zones.
Fixed some issues with missing subnets in ADDS Sites and Services.
Double and triple checked my IPv6 setup.
Ensured the firewall was enabled.

At last I found the issue that probably broke the proverbial camels back:
No connection could be made because the target machine actively refused it 127.0.0.1:890

The local firewall blocked local traffic from 120.0.0.1 to 127.0.0.1:890!

My guess is that this is because of our strict GPOs (WS2012R2 SCM baselines and the national security authorities’ GPOs).

The solution:

Put all the Exchange related Inbound FW rules in a GPO that had a higher precedence than our strict GPOs.
Restarted the Exchange-server-to-be.
Installed Exchange 2016 successfully!

Источник

Hello,

So today, somehow our Exchange server had the trust relationship issue where it was unable to sign in with the domain account.

I stopped services as I saw in another article, removed the PC from the domain, and rejoined it. When I booted the PC back up, I have about 17 services that are unable to start. I am unable to connect with ECP, OWA, or through Outlook.

I looked through the event log, and I see the following error, Audit Security Privilege on the DC.

I went into my DC and confirmed that the Exchange account is added into the audit and security logs.

I went ahead and ran the prepareAD and preparedomain commands again as suggested somewhere else, but the prepared domain gave me errors that went away too quickly for me to see.

ANy help would be apprecaited as I am out of ideas.

Источник

Remove From My Forums

Question
Hi experts

When trying to install another Exchange 2013 server in my test environment I got the following 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 settingshared config DC. Exception: » + $_.Exception.Message);
}

Write-ExchangeSetupLog -Info («Waiting 30 seconds before attemptingagain.»);
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.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)».

The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.

Did I miss anything? Any solution to this ?

Answers

Hi Hunk8,

Did this error happen when the setup program configuring the mailbox role:transport service and failed?

Are you able to ping the domain controller? Was windows server able to find it?

To Resolve This Issue, Follow The Below Steps.
1. Locate Microsoft.Exchange.Directory.TopologyService.exe.config File , By Default It Should Be Under «C:Program FilesMicrosoftExchange ServerV15Bin»
2. Open NotePad As Administrator & Then Open Microsoft.Exchange.Directory.TopologyService.exe.config File
3. Locate «Topology MinimumPrefixMatch»
4. Add MinSuitableServer = «1»
5. Save The File & Restart Microsoft Exchange Active Directory Topology Services.

Regards,

Beverly Gao

Please remember to
mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
tnsf@microsoft.com.
- Marked as answer by
  
  Thursday, December 19, 2019 2:41 PM

Источник

Question

Answers

Question

Answers