sync-generic-failure in Azure AD Connect Server

%3CLINGO-SUB%20id%3D%22lingo-sub-622366%22%20slang%3D%22en-US%22%3ERe%3A%20sync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-622366%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20things%20to%20try%20from%20the%20interweb%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*%20run%20a%20full%20import%20on%20the%20external%20connector%20(O365)%2C%20wait%20for%20the%20to%20complete.%20Then%20run%20a%20full%20import%20on%20the%20%26nbsp%3B%20domain%20connector.%20%3CBR%20%2F%3E%26nbsp%3BThen%20a%20full%20sync%20on%20each%20connector%20running%20the%20O365%20one%20first%20then%20and%20Export%20and%20then%20a%20Delta%20Sync.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*%20Could%20you%20reinstall%20your%20Azure%20AD%20connector%20to%20see%20if%20the%20issue%20persists%3F%3CBR%20%2F%3EAlso%2C%20make%20sure%20you%20enable%20port%20443%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-622402%22%20slang%3D%22en-US%22%3ERe%3A%20sync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-622402%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20check%20this%20and%20get%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20error%20only%20appears%20to%20external%20contacts%20in%20AD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-622294%22%20slang%3D%22en-US%22%3Esync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-622294%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20day!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20encountered%20this%20error%20during%20delta%20synchronization%20in%20Azure%20AD%20Connect%20Server%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%3A%20sync-generic-failure%3C%2FP%3E%3CP%3ESynchronization%20step%3A%20Provisioning%3C%2FP%3E%3CP%3EExtension%20Name%3A%20SyncRulesEngine%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-622294%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-636578%22%20slang%3D%22en-US%22%3ERe%3A%20sync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-636578%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20asked%20the%20customer%20to%20do%20a%20full%20sync%20but%20errors%20are%20still%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20addition%2C%20they%20are%20not%20configured%20for%20a%20password%20write%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-636931%22%20slang%3D%22en-US%22%3ERe%3A%20sync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-636931%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F345497%22%20target%3D%22_blank%22%3E%40MaryYvette%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20an%20OU%20in%20your%20On%20Prem%20AD%20that%20you%20do%20not%20Sync%20to%20Azure%20AD%3F%3C%2FP%3E%3CP%3EIf%20not%2C%20create%20an%20OU%20and%20update%20the%20Azure%20AD%20Connect%20configuration%20to%20not%20include%20that%20OU.%3C%2FP%3E%3CP%3EThen%3A%3C%2FP%3E%3COL%3E%3CLI%3EMove%20the%20On%20Prem%20object%20to%20that%20excluded%20OU%3C%2FLI%3E%3CLI%3ERun%20a%20delta%20sync%20using%20PowerShell%3C%2FLI%3E%3CLI%3EImport-Module%20ADSync%26nbsp%3B%20%23%20only%20needed%20if%20the%20ADSync%20module%20is%20not%20loaded%3C%2FLI%3E%3CLI%3EStart-ADSyncSyncCycle%20-PolicyType%20Delta%3C%2FLI%3E%3CLI%3EThen%20move%20the%20object%20back%20to%20its%20original%20location%2C%20and%20run%20another%20delta%20sync%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-636968%22%20slang%3D%22en-US%22%3ERe%3A%20sync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-636968%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20they%20are%20external%20contact%20make%20sure%20the%20mail%20attribute%20is%20correctly%20populated%20and%20also%20make%20sure%20in%20the%20instalation%20guide%20you%20selected%20for%20the%20users%20to%20be%20matched%20with%20the%20mail%20attribute%2C%20as%20per%20the%20Contact%20topic%20in%20the%20article%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Fconcept-azure-ad-connect-sync-user-and-contacts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Fconcept-azure-ad-connect-sync-user-and-contacts%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-651017%22%20slang%3D%22en-US%22%3ERe%3A%20sync-generic-failure%20in%20Azure%20AD%20Connect%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-651017%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F347260%22%20target%3D%22_blank%22%3E%40AliceIoanffa%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20you%20referring%20to%20UPN%2C%20TargetAddress%20and%20ProxyAddress%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Good day!

 

Has anyone encountered this error during delta synchronization in Azure AD Connect Server?

 

Error: sync-generic-failure

Synchronization step: Provisioning

Extension Name: SyncRulesEngine AAD Error.PNG

 

Thank you in advance!

6 Replies
Highlighted

@MaryYvette 

 

Some things to try from the interweb :

 

* run a full import on the external connector (O365), wait for the to complete. Then run a full import on the   domain connector.
 Then a full sync on each connector running the O365 one first then and Export and then a Delta Sync.

 

* Could you reinstall your Azure AD connector to see if the issue persists?
Also, make sure you enable port 443

Highlighted

@adam deltinger 

 

Will check this and get back.

 

The error only appears to external contacts in AD.

 

Thanks.

Highlighted

@adam deltinger 

 

I asked the customer to do a full sync but errors are still there.

 

In addition, they are not configured for a password write back.

 

Thanks.

Highlighted

@MaryYvette 

 

Do you have an OU in your On Prem AD that you do not Sync to Azure AD?

If not, create an OU and update the Azure AD Connect configuration to not include that OU.

Then:

  1. Move the On Prem object to that excluded OU
  2. Run a delta sync using PowerShell
  3. Import-Module ADSync  # only needed if the ADSync module is not loaded
  4. Start-ADSyncSyncCycle -PolicyType Delta
  5. Then move the object back to its original location, and run another delta sync
Highlighted

If they are external contact make sure the mail attribute is correctly populated and also make sure in the instalation guide you selected for the users to be matched with the mail attribute, as per the Contact topic in the article: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/concept-azure-ad-connect-sync-user-an...

Highlighted

@AliceIoanffa 

 

Are you referring to UPN, TargetAddress and ProxyAddress?