Freigeben über

Exchange 2013 Setup Fails With Error "An exception ocurred while setting shared config DC"

  • Artikel

While Working On Exchange 2013 Setup Support Case, The Setup Failed With Below Error

However We Were Able To Ping & Windows Server Was Able To Find All Domain Controller In The Site

Configuring Microsoft Exchange Server

    Preparing Setup COMPLETED
    Stopping Services COMPLETED
    Copying Exchange Files COMPLETED
    Language Files COMPLETED
    Restoring Services COMPLETED
    Language Configuration COMPLETED
    Mailbox role: Transport service FAILED
     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.

Log Name: Application
Source: MSExchangeADTopology
Date: 7/9/2015 4:09:27 PM
Event ID: 2142
Task Category: (3)
Level: Error
Keywords: Classic
User: N/A
Computer: XXXX.XXXX
Description:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2848) Forest xxxxx. Topology discovery failed, error details
No Minimal Required Number of Suitable Directory Servers Found in Forest xxxxx Site xxxxx and connected Sites..

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 Files\Microsoft\Exchange Server\V15\Bin"

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.

This Should Resolve The Issue.

Note : This Resolution May Or May Not Apply Depending On The Error.

Comments

  • Anonymous
    July 10, 2015
    thanks
    very interesting
  • Anonymous
    September 24, 2015
    thanks. interesteng and helped me
  • Anonymous
    November 15, 2015
    I had the same issue , however ,I got the same error even in my old exchange server which they were working properly .I added that key then the 4027 & 2142 are stopped ,all exchange servers worked .

    but I don't know what is the cause of that issue .

  • Anonymous
    February 13, 2016
    It seems helped me on exchange 2016 setup
  • Anonymous
    April 03, 2016
    thank you, it helped me !