AAD sync stopped working

Question

Hi All,

We currently have AAD setup and it's been working up until last week (Scheduling)

when I check to see the schedule, I get:

AllowedSyncCycleInterval : 00:30:00

CurrentlyEffectiveSyncCycleInterval : 00:30:00

CustomizedSyncCycleInterval :

NextSyncCyclePolicyType : Delta

NextSyncCycleStartTimeInUTC : 3/07/2016 10:28:28 PM

PurgeRunHistoryInterval : 7.00:00:00

SyncCycleEnabled : True

MaintenanceEnabled : False

StagingModeEnabled : False

It looks good from this, but it doesn't run.. 

When I run: Start-ADSyncSyncCycle -PolicyType Initial (Manual sync) - It works fine.

Is there something I can do to get it to work again? Again, just want to clarify it WAS working up until Friday last week

Thanks,

Vincent

Answer 1

Hi Vincent,

Thanks for your feedback.

I have checked the log file you provided, and found that the main error is Event ID 906, and the detailed error message says “Scheduler::SchedulerThreadMain : Encountered error while waiting for signal.”

Based on my research, this error is a known issue reported by several users in March. And the suggested solution is to upgrade your AAD Connect tool to the latest version 1.1.110.0: https://www.microsoft.com/en-us/download/details.aspx?id=47594

Please give it a shot, and feel free to let me know if the issue persists.

Regards,

Allen

Answer 2

We had exactly the same issue, and upgrading to version 1.1.110.0 resolved the issue. Thanks!

Answer 3

I have sent you the file

Thanks,

Vincent

Answer 4

Vincent, curious of what conclusions you get when you run the directory synchronization diagnostic.  It's best to run it from the sync server itself if you can, although you can run it remotely with limited functionality.  You can enter into the workflow from http://aka.ms/dsup

Answer 5

Hi Vincent,

I see that you can run the Start-ADSyncSyncCycle command to force the synchronization, and I’d like to know the actual symptom about the issue. Can all the new changes or updates from the on-premises AD not be synchronized at all to Office 365?

Moreover, in order to further troubleshoot it, please provide the Event Viewer logs regarding Directory Synchronization services. Please see the steps of collecting the logs:

1. Open the Event Viewer on your AAD Connect server.
2. In the left panel, select Windows Logs -> Application. Right-click Application and select Create Custom View.
3. Select By source and choose ADSync as the Event sources.
4. Click OK to let it run, and see if you can find any errors. Warnings could be just ignored.

Considering that the logs may contain your privacy information, I have sent you a private message to collect them. Please see it at https://community.office365.com/user/conversations

Thanks,

Allen