Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Batling with Exchange 2013 repair

Posted on 2015-01-17
1
Medium Priority
?
132 Views
Last Modified: 2015-01-21
Hi Everyone

I did try most articles on this website and I'm still not able to get the repair run on exchange 2013 ,I did disable  Firewall ,IPV6 is enabled on all servers and the server can read the FQDN on the domain controller. There is also no old AD servers and so on.

Herewith message again


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.";

Please let me know what else I can try.

Thanks
SD
0
Comment
Question by:Dirkie Laubscher
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 20

Accepted Solution

by:
compdigit44 earned 2000 total points
ID: 40558805
I hate to say this but at this point you may be better off build a new Exchange server, manually remove the old one the restore all data..

 http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question