none
MIM 2016 R2 sync-rule-invalid-xml-attribute-flow RRS feed

  • Question

  • I seem to have triggered this error message in multiple MAs (management agents) "sync-rule-invalid-xml-attribute-flow" for multiple user objects in a small AD test environment. But only one attribute that looks normal in the sync engine is appearing which have never caused problems in this test environment before. 

    I also get CS to MV to CS synchronization failed 0x80230554 on the AD MA.

    Same for FIMMA. and with 2 other core MAs and then references what looks to be a Sync Rule GUID out on the FIMService. 

    I'm at a loss as to how to track this down. Luckily its a test environment, so I can do my worst and hopefully learn or help someone out. Thanks

    Monday, October 14, 2019 10:38 PM

All replies

  • Hi,

    What version of MIM are you on? There's a bug in one of the later hotfixes that can cause this. FI/FS should solve the problem.

    Br,
    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Tuesday, October 15, 2019 7:04 AM
  • Hi Leo,

    I'm on R2 4..4.1749.0.

    Thanks,

    Marc

    Tuesday, October 15, 2019 3:21 PM
  • Found this SQL Error in the event viewer. 

    The server encountered an unexpected error and stopped.
     
     "WARNING: MMS(2520): ..\sql.cpp(5342): Error retrieving error
    BAIL: MMS(2520): ..\sql.cpp(557): 0x80230406 (An error has occurred at the store)
    BAIL: MMS(2520): ..\sql.cpp(513): 0x80230406 (An error has occurred at the store)
    BAIL: MMS(2520): ..\sql.cpp(349): 0x80230406 (An error has occurred at the store)
    BAIL: MMS(2520): ..\storeimp.cpp(282): 0x80230406 (An error has occurred at the store)
    ERR_: MMS(2520): ..\server.cpp(400): Failed to connect to the database FIMSynchronizationService on SyncServer
    BAIL: MMS(2520): ..\server.cpp(401): 0x80230406 (An error has occurred at the store)
    BAIL: MMS(2520): ..\server.cpp(3945): 0x80230406 (An error has occurred at the store)
    BAIL: MMS(2520): ..\service.cpp(1585): 0x80230406 (An error has occurred at the store)
    ERR_: MMS(2520): ..\service.cpp(1024): Error creating com objects. Error code: -2145188858. This is retry number 0.
    BAIL: MMS(2520): ..\CLRHost.cpp(225): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\ScriptManagerImpl.cpp(7894): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\server.cpp(259): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\server.cpp(3945): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\service.cpp(1585): 0x80131022 (unable to get error text)
    ERR_: MMS(2520): ..\service.cpp(1024): Error creating com objects. Error code: -2146234334. This is retry number 1.
    BAIL: MMS(2520): ..\CLRHost.cpp(225): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\ScriptManagerImpl.cpp(7894): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\server.cpp(259): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\server.cpp(3945): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\service.cpp(1585): 0x80131022 (unable to get error text)
    ERR_: MMS(2520): ..\service.cpp(1024): Error creating com objects. Error code: -2146234334. This is retry number 2.
    BAIL: MMS(2520): ..\CLRHost.cpp(225): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\ScriptManagerImpl.cpp(7894): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\server.cpp(259): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\server.cpp(3945): 0x80131022 (unable to get error text)
    BAIL: MMS(2520): ..\service.cpp(1585): 0x80131022 (unable to get error text)
    ERR_: MMS(2520): ..\service.cpp(1024): Error creating com objects. Error code: -2146234334. This is retry number 3.
    BAIL: MMS(2520): ..\service.cpp(1038): 0x80131022 (unable to get error text)
    Forefront Identity Manager 4.4.1749.0"

    Tuesday, October 15, 2019 3:44 PM
  • Hi,

    That looks like a database connection error. Please ensure that the database is running.

    Br

    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Wednesday, October 16, 2019 6:41 AM
  • After comparing this test environment with prod, I found (back in the first instance of the error in Operations) that a schema refresh in test on the HR MA cleared out a manager attribute that was set to Reference(DN) and made it a String. After editing this back to Reference(DN), this error went away on all user objects in all the various MAs showing this error and syncs are back to normal. There is an article about this already posted, but this cleared up my issue. 
    • Proposed as answer by Leo Erlandsson Thursday, October 17, 2019 6:18 AM
    Wednesday, October 16, 2019 4:09 PM