Home

Error event logs from ADSync - How to troubleshoot

%3CLINGO-SUB%20id%3D%22lingo-sub-1187382%22%20slang%3D%22en-US%22%3EError%20event%20logs%20from%20ADSync%20-%20How%20to%20troubleshoot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1187382%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20we%20are%20using%20the%20latest%20ADSync%20as%20of%20this%20post%2C%201.4.38.0.%26nbsp%3B%20As%20far%20as%20we%20can%20tell%20nothing%20is%20broken.%26nbsp%3B%20The%20only%20purpose%20of%20this%20tool%20is%20to%20allow%20Office%20365%20to%20be%20assigned%20to%20our%20domain%20users%20and%20verify%20licencing%20%2F%20entitlements.%26nbsp%3B%20We%20are%20not%20doing%20anything%20else%20in%20the%20cloud%20and%20our%20Exchange%2C%20Skype%20for%20business%20is%20on%20prem%20at%20this%20point.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20getting%20these%20logs%20from%20our%20server%20called%20ADFS1%20which%20had%20the%20ADSync%20tool%20installed.%26nbsp%3B%20I'm%20not%20sure%20what%20to%20do%20with%20them%20because%20it%20seems%20everything%20is%20working%20fine.%26nbsp%3B%20I%20would%20like%20to%20know%20if%20there's%20a%20way%20to%20silence%20these%20alerts%20without%20filtering%20them%20out%20of%20our%20EventSentry%20log%20management%20system.%26nbsp%3B%20We%20are%20just%20tired%20of%20seeing%20these%20alerts%20to%20our%20email.%26nbsp%3B%20Below%20is%20a%20sample%20of%20what%20we%20wee%20multiple%20times%20a%20day%2C%20about%20once%20every%20hour.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20width%3D%22100%25%22%3E%3CTBODY%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20%23%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E5182516%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20LOG%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EApplication%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20TYPE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E%3CSTRONG%3EError%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EOPCODE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EInfo%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ESOURCE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EADSync%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ECATEGORY%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EServer%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20ID%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E6311%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EDATE%20%2F%20TIME%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E2%2F21%2F2020%2010%3A42%3A46%20AM%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ECOMPUTERNAME%26nbsp%3B%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EADFS1%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EMESSAGE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EThe%20server%20encountered%20an%20unexpected%20error%20while%20performing%20a%20callback%20operation.%3CBR%20%2F%3E%3CBR%20%2F%3E%22ERR_%3A%20MMS(6640)%3A%20..%5Cma.cpp(4898)%3A%20Completing%20apply%20rules%20step%20has%20failed.%3CBR%20%2F%3EAzure%20AD%20Sync%201.4.38.0%22%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20width%3D%22100%25%22%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20%23%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E5182517%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20LOG%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EApplication%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20TYPE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E%3CSTRONG%3EError%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EOPCODE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EInfo%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ESOURCE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EADSync%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ECATEGORY%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EServer%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20ID%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E6401%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EDATE%20%2F%20TIME%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E2%2F21%2F2020%2010%3A42%3A46%20AM%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ECOMPUTERNAME%26nbsp%3B%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EADFS1%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EMESSAGE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EThe%20management%20agent%20controller%20encountered%20an%20unexpected%20error.%3CBR%20%2F%3E%3CBR%20%2F%3E%22ERR_%3A%20MMS(6640)%3A%20..%5Ccrcntrl.cpp(336)%3A%20Completing%20synchronization%20run%20step%20has%20failed.%3CBR%20%2F%3EAzure%20AD%20Sync%201.4.38.0%22%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20width%3D%22100%25%22%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20%23%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E5182518%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20LOG%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EApplication%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20TYPE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EWarning%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EOPCODE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EInfo%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ESOURCE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EADSync%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ECATEGORY%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EManagement%20Agent%20Run%20Profile%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EEVENT%20ID%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E6100%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EDATE%20%2F%20TIME%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3E2%2F21%2F2020%2010%3A42%3A46%20AM%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3ECOMPUTERNAME%26nbsp%3B%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EADFS1%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2215%25%22%3E%3CP%3EMESSAGE%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2285%25%22%3E%3CP%3EThe%20management%20agent%20%22domain.com%22%20step%20execution%20completed%20on%20run%20profile%20%22Delta%20Synchronization%22%20with%20errors.%3CBR%20%2F%3E%3CBR%20%2F%3EAdditional%20Information%3CBR%20%2F%3EDiscovery%20Errors%20%3A%20%220%22%3CBR%20%2F%3ESynchronization%20Errors%20%3A%20%221%22%3CBR%20%2F%3EMetaverse%20Retry%20Errors%20%3A%20%220%22%3CBR%20%2F%3EExport%20Errors%20%3A%20%220%22%3CBR%20%2F%3EWarnings%20%3A%20%220%22%3CBR%20%2F%3E%3CBR%20%2F%3EUser%20Action%3CBR%20%2F%3EView%20the%20management%20agent%20run%20history%20for%20details.%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1187382%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EADSync%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1187600%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20event%20logs%20from%20ADSync%20-%20How%20to%20troubleshoot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1187600%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E6100%3C%2FSPAN%3E%20is%20pretty%20normal%2C%20and%20the%20other%20two%20are%20always%20logged%20in%20conjunction%20with%20it.Here's%20the%20actual%20explanation%20from%20the%20documentation%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20margin-top%3A%200px%3B%20margin-bottom%3A%2016px%3B%20color%3A%20%2324292e%3B%20font-family%3A%20-apple-system%2C%20BlinkMacSystemFont%2C%20'Segoe%20UI'%2C%20Helvetica%2C%20Arial%2C%20sans-serif%2C%20'Apple%20Color%20Emoji'%2C%20'Segoe%20UI%20Emoji'%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20start%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20white-space%3A%20normal%3B%20widows%3A%202%3B%20word-spacing%3A%200px%3B%20-webkit-text-stroke-width%3A%200px%3B%20background-color%3A%20%23ffffff%3B%20text-decoration-style%3A%20initial%3B%20text-decoration-color%3A%20initial%3B%22%3E%3CSTRONG%20style%3D%22box-sizing%3A%20border-box%3B%20font-weight%3A%20600%3B%22%3EQ%3A%20Why%20am%20I%20seeing%20Events%206311%20and%206401%20occur%20after%20Sync%20Step%20Errors%3F%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20margin-top%3A%200px%3B%20margin-bottom%3A%200px%20!important%3B%20color%3A%20%2324292e%3B%20font-family%3A%20-apple-system%2C%20BlinkMacSystemFont%2C%20'Segoe%20UI'%2C%20Helvetica%2C%20Arial%2C%20sans-serif%2C%20'Apple%20Color%20Emoji'%2C%20'Segoe%20UI%20Emoji'%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20start%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20white-space%3A%20normal%3B%20widows%3A%202%3B%20word-spacing%3A%200px%3B%20-webkit-text-stroke-width%3A%200px%3B%20background-color%3A%20%23ffffff%3B%20text-decoration-style%3A%20initial%3B%20text-decoration-color%3A%20initial%3B%22%3EThe%20events%206311%20-%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%20style%3D%22box-sizing%3A%20border-box%3B%20font-weight%3A%20600%3B%22%3EThe%20server%20encountered%20an%20unexpected%20error%20while%20performing%20a%20callback%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%206401%20-%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%20style%3D%22box-sizing%3A%20border-box%3B%20font-weight%3A%20600%3B%22%3EThe%20management%20agent%20controller%20encountered%20an%20unexpected%20error%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E-%20are%20always%20logged%20after%20a%20synchronization%20step%20error.%20To%20resolve%20these%20errors%2C%20you%20need%20to%20clean%20up%20the%20synchronization%20step%20errors.%20For%20more%20information%2C%20see%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20style%3D%22box-sizing%3A%20border-box%3B%20background-color%3A%20initial%3B%20color%3A%20%230366d6%3B%20text-decoration%3A%20none%3B%22%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Factive-directory%2Fhybrid%2Ftshoot-connect-sync-errors.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ETroubleshooting%20errors%20during%20synchronization%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20style%3D%22box-sizing%3A%20border-box%3B%20background-color%3A%20initial%3B%20color%3A%20%230366d6%3B%20text-decoration%3A%20none%3B%22%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Factive-directory%2Fhybrid%2Ftshoot-connect-objectsync.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ETroubleshoot%20object%20synchronization%20with%20Azure%20AD%20Connect%20sync%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

First we are using the latest ADSync as of this post, 1.4.38.0.  As far as we can tell nothing is broken.  The only purpose of this tool is to allow Office 365 to be assigned to our domain users and verify licencing / entitlements.  We are not doing anything else in the cloud and our Exchange, Skype for business is on prem at this point.

 

We are getting these logs from our server called ADFS1 which had the ADSync tool installed.  I'm not sure what to do with them because it seems everything is working fine.  I would like to know if there's a way to silence these alerts without filtering them out of our EventSentry log management system.  We are just tired of seeing these alerts to our email.  Below is a sample of what we wee multiple times a day, about once every hour.

 

Any ideas?

 

EVENT #

5182516

EVENT LOG

Application

EVENT TYPE

Error

OPCODE

Info

SOURCE

ADSync

CATEGORY

Server

EVENT ID

6311

DATE / TIME

2/21/2020 10:42:46 AM

COMPUTERNAME 

ADFS1

MESSAGE

The server encountered an unexpected error while performing a callback operation.

"ERR_: MMS(6640): ..\ma.cpp(4898): Completing apply rules step has failed.
Azure AD Sync 1.4.38.0"

 

 

EVENT #

5182517

EVENT LOG

Application

EVENT TYPE

Error

OPCODE

Info

SOURCE

ADSync

CATEGORY

Server

EVENT ID

6401

DATE / TIME

2/21/2020 10:42:46 AM

COMPUTERNAME 

ADFS1

MESSAGE

The management agent controller encountered an unexpected error.

"ERR_: MMS(6640): ..\crcntrl.cpp(336): Completing synchronization run step has failed.
Azure AD Sync 1.4.38.0"

 

 

EVENT #

5182518

EVENT LOG

Application

EVENT TYPE

Warning

OPCODE

Info

SOURCE

ADSync

CATEGORY

Management Agent Run Profile

EVENT ID

6100

DATE / TIME

2/21/2020 10:42:46 AM

COMPUTERNAME 

ADFS1

MESSAGE

The management agent "domain.com" step execution completed on run profile "Delta Synchronization" with errors.

Additional Information
Discovery Errors : "0"
Synchronization Errors : "1"
Metaverse Retry Errors : "0"
Export Errors : "0"
Warnings : "0"

User Action
View the management agent run history for details.

1 Reply
Highlighted

6100 is pretty normal, and the other two are always logged in conjunction with it.Here's the actual explanation from the documentation: 

 

Q: Why am I seeing Events 6311 and 6401 occur after Sync Step Errors?

The events 6311 - The server encountered an unexpected error while performing a callback and 6401 - The management agent controller encountered an unexpected error - are always logged after a synchronization step error. To resolve these errors, you need to clean up the synchronization step errors. For more information, see Troubleshooting errors during synchronization and Troubleshoot object synchronization with Azure AD Connect sync