This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 53%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDS%3C/text%3E%3C/svg%3E)
I opened up AD connect and it's requiring that i do an "upgrade" however after it goes through a bit of the process it finally comes back and just says that it failed. looking through the log it sorta looks like the AD sync server takes too long but it does eventually come back. although maybe this isn't even related to the actual issue. can someone take a look at this and see what's going on?
Here's the trace file: trace-20230817-123630-CENSORED.log
and here's an image of the error: AD Connect Failure error.png
I've tried to download a new AD connect V2 and repair the installation but this doesn't help.
Going threw the same problem but with a clean install , ((Get-MSOLCompanyInformation).DirectorySynchronizationEnabled) is set to false Set-ADSyncScheduler -SyncCycleEnabled $true fails , one blog said its a permissions issue PersistedState.xml , still fails , this is show stopper
o
yea i was able to figure out how to re-enable sync thankfully. you said even after re-install you're still experiencing the issue? i did a config backup and was going to attempt a re-install today but sounds like this won't solve it?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 44%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Whether on Azure or our lab, we rebuilt domain controller and setup several times, we popup this error everytimes, even we install the previous v2 version, It didn't solve.
We had tried to change the DNS to 8.8.8.8. Not Work
We had tried in customized or express settings. Same error still.
We had tried to run "set-msoldirsyncenabled" on powershell, or delete unverified domain. Same error still.
The problem slove today, and I haven't change any setting, just reinstall and retry, both azure vm and lab's AADC can both connect to their own tanent, I believe there are some abnormal situation about AADC service from Microsoft during 08/21(Mon) to 08/22(Tue).