This happens at random times of the day, but primarily, early in the morning; most recently 7:30AM, AD Connect will just stop attempting to sync. I am currently running Windows Server 2016 Datacenter. Ad Connect version 1.4.38.0. When I attempt to force a delta sync, I receive the error at the bottom. I have attempted to see if the process was held for some reason, but I can't find any instance. I have also tried to restart the process via the Services window, but that did not work either. The ADSyncScheduler says everything is fine. I only came into this environment a few weeks ago and am still learning how everything is setup. Not sure if its pertinent info, but the server itself is rebooted everyday at 1:30AM.
Start-ADSyncSyncCycle : System.InvalidOperationException: Azure AD Connect scheduler is unable to start a new sync
cycle because Azure AD Connect wizard is open. Please close the wizard if it is not in use.
at Microsoft.MetadirectoryServices.Scheduler.Scheduler.StartSyncCycle(String overridePolicy, Boolean
interactiveMode)
at SchedulerUtils.StartSyncCycle(SchedulerUtils* , Char* policyType, Int32 interactiveMode, Char** errorString)
At line:1 char:1
+ Start-ADSyncSyncCycle -Policytype Delta
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (Microsoft.Ident...ADSyncSyncCycle:StartADSyncSyncCycle) [Start-ADSyncSyncCy
cle], InvalidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException: Azure AD Connect scheduler is unable to start a new sy
nc cycle because Azure AD Connect wizard is open. Please close the wizard if it is not in use.
at Microsoft.MetadirectoryServices.Scheduler.Scheduler.StartSyncCycle(String overridePolicy, Boolean interactiv
eMode)
at SchedulerUtils.StartSyncCycle(SchedulerUtils* , Char* policyType, Int32 interactiveMode, Char** errorString)
,Microsoft.IdentityManagement.PowerShell.Cmdlet.StartADSyncSyncCycle