Dec 07 2018
04:17 PM
- last edited on
Jan 14 2022
05:21 PM
by
TechCommunityAP
Dec 07 2018
04:17 PM
- last edited on
Jan 14 2022
05:21 PM
by
TechCommunityAP
Hello,
In my test system there is problem with ad-connect. It stocks by the step delta-import for days
Tanks for your help
Stefan
Dec 08 2018 07:13 AM
If it's a test machine just restart it. Or you can just restart the AAD Sync service instead :)
Dec 09 2018 08:56 AM
It is still the same problem I restarted the server and the Service.
Dec 09 2018 09:02 AM
Check the event logs then, there might be some events there to give you a clue what's going on.
Dec 09 2018 09:27 AM
Dec 09 2018 11:57 AM - edited Dec 09 2018 01:11 PM
Full sync starts via PowerShell or with ad connects runs without any problems. Only the delta Import brings the problems
I find three log entries:
Failure while prefetching import data. More details at: https://go.microsoft.com/fwlink/?linkid=869679. Exception message: Failed even after 5 retries. Action: ImportV1, Network error occurrences = 0. Exception: The Windows Azure Active Directory service is temporarily unavailable. If you continue to see this issue, contact Technical Support.
Failure while importing entries from Windows Azure Active Directory. More details at: https://go.microsoft.com/fwlink/?linkid=869679. Exception message: Failed even after 5 retries. Action: ImportV1, Network error occurrences = 0. Exception: The Windows Azure Active Directory service is temporarily unavailable. If you continue to see this issue, contact Technical Support.
The management agent "dev.onmicrosoft.com - AAD" failed on run profile "Delta Import" because the server encountered errors.
Dec 10 2018 09:49 AM
That does look like a connectivity issue, have you checked the steps in the article they are referencing? https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-connectivity
Dec 11 2018 02:46 AM
Yes I had checkt it.
Why is the network problem only in this one step and all other steps works fine.
Dec 12 2018 06:28 AM
SolutionThis Powershell commands solved my problem
Set-ADSyncScheduler -SyncCycleEnabled $FALSE
Start-ADSyncSyncCycle -PolicyType Initial
Start-ADSyncSyncCycle -PolicyType Delta
Set-ADSyncScheduler -SyncCycleEnabled $TRUE
Dec 12 2018 09:28 AM
Interesting, so it simply needed a full sync. Cant say I've seen such behavior previously...
Dec 12 2018 06:28 AM
SolutionThis Powershell commands solved my problem
Set-ADSyncScheduler -SyncCycleEnabled $FALSE
Start-ADSyncSyncCycle -PolicyType Initial
Start-ADSyncSyncCycle -PolicyType Delta
Set-ADSyncScheduler -SyncCycleEnabled $TRUE