none
Need-Full-Object in Call based ECMA2 (Sync server crashes if too many objects) RRS feed

  • Question

  • Hello,
    i have a very strange problem when doing delta imports in our ECMA2. First, something about delta import from ECMA2 docs:

    "The mode “Full Object Import” goes with Delta import is invoked by the engine when a batch returns updates to objects for which there is no representation in the connector space. Since the engine can’t determine how the new object should look like this method is called with a list of object identifiers for which the engine need a full object representation."

    Now this led me to believe that when importing a completely new object during DI, sync engine will call the method GetImportEntries with importType "FullObjectImport", which is not the case. It does however fill the FullObjectEntries parameter with entries that it needs a full representation of and calls the GetImportEntries method again, with "Delta" importType. So i changed my import logic to return a full representation for these objects on the next call in case there are any. And this is where things start to get strange. It works perfectly fine for 0-100 (varies) objects, but for a delta import that returns let's say 400 objects that are "new", this  will always crash the sync service

    So my question is does anyone have an idea how to deal with need-full-object requests in an ECMA2 delta import that requires objects to have ObjectModificationType Update and not Add?

    Below is the error code:

    Faulting application name: miiserver.exe, version: 4.1.3671.0, time stamp: 0x55f937ba
    Faulting module name: ntdll.dll, version: 6.3.9600.18233, time stamp: 0x56bb4ebb
    Exception code: 0xc0000374
    Fault offset: 0x00000000000f1b70
    Faulting process id: 0xf44
    Faulting application start time: 0x01d1bbd23e2b1264
    Faulting application path: E:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 536232e7-27c8-11e6-80d9-0050569508de
    Faulting package full name: 
    Faulting package-relative application ID: 

    and this:

    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: miiserver.exe
    P2: 4.1.3671.0
    P3: 55f937ba
    P4: StackHash_6e3d
    P5: 6.3.9600.18233
    P6: 56bb4ebb
    P7: c0000374
    P8: PCH_33_FROM_ntdll+0x00000000000F1B70
    P9: 
    P10: 

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_miiserver.exe_61d31a1751356f3ce935aa81f2382165d0831d57_c8ce2d5c_2ea109b3

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 536232e7-27c8-11e6-80d9-0050569508de
    Report Status: 4100
    Hashed bucket: 


    Wednesday, June 1, 2016 7:49 AM

All replies

  • Hi,

    Did you manage to resolve this? I have the same issue, but it helps if I change the run profile page size to i.e. 500 and the number of full-objects are below this.

    Thanks,

    Soren


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Monday, January 29, 2018 3:58 PM