none
FIM 2010 - 300+ staging errors on GAL SYNC MA????? RRS feed

  • Question

  • I have several FIM 2010 GAL Synch MA's set up with external Exchange org's.  I have a couple of MA's that are throwing 300 + staging errors (see event log below) which of course prevents an export from taking place.  Any suggestions?

    Description:
    The server encountered an unexpected error in the synchronization engine:
     
     "BAIL: MMS(3076): hobl.cpp(4148): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): _images.h(1853): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tripleholo.cpp(17206): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tripleholo.cpp(16798): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tower.cpp(7641): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tower.cpp(1398): 0x80004005 (Unspecified error)
    <delta operation="replace"  <primary-objectclass>contact</primary-objectclass>
     <objectclass>
      connector>1</connector><connector-state>normal</connector-state><seen-by-import>0</seen-by-import><rebuild-in-progress>0</rebuild-in-progress><obsoletion>0</obsoletion><need-full-sync>0</need-full-sync><placeholder-parent>0</placeholder-parent><placeholder-link>0</placeholder-link><placeholder-delete>0</placeholder-delete><pending>0</pending><ref-retry>0</ref-retry><rename-retry>0</rename-retry><sequencers><current><batch-number>3</batch-number><sequence-number>845340</sequence-number></current><unapplied><batch-number>3</batch-number><sequence-number>845340</sequence-number></unapplied><original><batch-number>3</batch-number><sequence-number>845340</sequence-number></original></sequencers><import-delta-operation>none</import-delta-operation><export-delta-operation>modify</export-delta-operation></tower>BAIL: MMS(3076): csobj.h(1375): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): syncstage.cpp(1697): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): syncstage.cpp(284): 0x80004005 (Unspecified error)
    ERR: MMS(3076): syncstage.cpp(333): 0x80004005 - staging failed 0x80004005
    ERR: MMS(3076): syncstage.cpp(334): Staging failed 0x80004005: ]ERR: MMS(3076): syncmonitor.cpp(2515): SE: Rollback SQL transaction for: 0x80004005
    MMS(3076): SE: CS image begin
    MMS(3076): <cs-object cs-dn="}" object-type="contact">
     <unapplied-export>
      <delta operation="update" dn="">
      MMS(3076): SE: CS image end
    Forefront Identity Manager 4.0.2592.0"
    Event Xml:
    <Event xmlns="  <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="49152">6301</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-07-15T09:23:36.000000000Z" />
        <EventRecordID>548978</EventRecordID>
        <Channel>Application</Channel>
        <Computer>    <Security />
      </System>
      <EventData>
        <Data>BAIL: MMS(3076): hobl.cpp(4148): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): _images.h(1853): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tripleholo.cpp(17206): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tripleholo.cpp(16798): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tower.cpp(7641): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): tower.cpp(1398): 0x80004005 (Unspecified error)
     csobj.h(1375): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): syncstage.cpp(1697): 0x80004005 (Unspecified error)
    BAIL: MMS(3076): syncstage.cpp(284): 0x80004005 (Unspecified error)
    ERR: MMS(3076): syncstage.cpp(333): 0x80004005 - staging failed 0x80004005
    ERR: MMS(3076): syncstage.cpp(334): Staging failed 0x80004005: [ERR: MMS(3076): syncmonitor.cpp(2515): SE: Rollback SQL transaction for: 0x80004005
    MMS(3076): SE: CS image begin
    MMS(3076): MMS(3076): SE: CS image end
    Forefront Identity Manager 4.0.2592.0</Data>
      </EventData>
    </Event>



    TAG

    Monday, July 16, 2012 4:07 PM

All replies

  • Quick update- did some research, and decided to Export to Drop File (Create log file and stop the run.  Do not export to data source (test only)) jsut to have a look.  The scheduled MA's ran fine that night with no staging errors, and succesfully exported to the data source.

    TAG

    Tuesday, July 24, 2012 3:21 PM
  • You don't happen to run a "synchronization run profile" on multiple MA's at the same time? In most situations it's strongly advised to not do this. Only imports and exports can be run at the same time for multiple MA's.

    It's just a guess, I might be very wrong as well :)


    http://setspn.blogspot.com

    Tuesday, July 24, 2012 8:48 PM
  • No,no synch's running at the same time - all MA's are set to run at different schedules


    TAG

    Tuesday, July 24, 2012 8:52 PM
  • Hi Theresa,

    can you provide detailed steps on what you did? I'm pretty new on Sharepoint / FIM and seeing same issues as you are.

    Wednesday, September 12, 2012 8:25 AM
  • Well, had to take a couple of approaches, try the below first

    -create new OU that is not in scope (so, in the MA, go to Configure Directory Partitions and ensure this new OU is NOT checked off)

    -move the objects that are throwing the staging errors to this OU

    -run delta import(stage only) run profile, look for deletes (you should see deletes for the objects that you have moved into the above, out of synch scope OU)

    -assuming you see deletes, move the objects from OU above to target OU (the original OU they were in)

    -run delta import(stage only) run profile again, look for adds and no staging errors

    -if no staging errors, this has been fixed

    This did work for one MA, but not for another.  So, I decided to a "Test Export" (drop to log file) so I could have a look at the output.  Magically (?!), the next scheduled run ran fine with no staging errors.  To do this:

    go to "Configure Run Profiles" for the MA

    Give it a name (TEST), then choose Export as the specified step type.

    Click on "Set log file Options" and choose "Create a log file and stop the run.  Do not export to data source (test only)"

    Choose the partition to run it on, and then run the test profile


    TAG

    Wednesday, September 12, 2012 5:27 PM