Hi, I am running into an issue where an xMA full import is throwing a discovery-error (Staging-error) on a particular user object. This user object has a modification type of Delete-add. An export has been of this object has been successfully submitted and it's currently waiting for export confirmation. Upon running full import on the xMA, the same object appears under discovery errors as Staging-error without any further information. Reviewing the event log, it seems that FIM is attempting to add an object to mms_connectorspace that has the same id (i.e. poobjectid) of an already existed object (below is the full error message). Disabled Provisioning Rules (Tools/Options) and attempted to Preview a full sync and see that the object is recognized as an 'export-phantom'. In order to convert the export-phantom object to an actual object (or export) the import must occur, but I am unable to do that due to the staging error. My only last try is to remove the staged-error object from the Table/View that the xMA is building its LDIF content from. That way, FIM seems the object is being delete (i.e. not existing in the LDIF), and hopefully delete the object from the CS. I'd like to know if this is going to work? or if there is any other options here? "ERR: MMS(4024): sql.cpp(5671): Query ({call mms_addcsobjwithpartition(?,?,?,?,?,?,?)}) performed with error ERR: MMS(4024): sql.cpp(5724): Cannot insert duplicate key row in object 'dbo.mms_connectorspace' with unique index 'IX_mms_connectorspacepobject_idrdnma_id'. ERR: MMS(4024): sql.cpp(5732): hrError: 0x80040e2f, dwMinor: 2601 ERR: MMS(4024): sql.cpp(5887): SQL error: 23000, native: 2601 BAIL: MMS(4024): sql.cpp(7381): 0x80040e2f BAIL: MMS(4024): sql.cpp(7185): 0x80040e2f ERR: MMS(4024): sproc.cpp(523): Please ignore the previous error. The error is benign. BAIL: MMS(4024): sproc.cpp(525): 0x8023040f (The object already exists) ERR: MMS(4024): sql.cpp(5671): Query ({call mms_releasemawritelock(?)}) performed with error ERR: MMS(4024): sql.cpp(5724): Cannot release the application lock (Database Principal: 'public', Resource: '{*****************************}') because it is not currently held. ERR: MMS(4024): sql.cpp(5732): hrError: 0x80040e14, dwMinor: 1223 ERR: MMS(4024): sql.cpp(5782): Error trying to release an applock that is not currently being held ERR: MMS(4024): sql.cpp(5887): SQL error: 42000, native: 1223 BAIL: MMS(4024): sql.cpp(7381): 0x8023043d (An attempt was made to release a lock that has not been acquired) BAIL: MMS(4024): sql.cpp(7185): 0x8023043d (An attempt was made to release a lock that has not been acquired) BAIL: MMS(4024): sproc.cpp(3135): 0x8023043d (An attempt was made to release a lock that has not been acquired) ERR: MMS(4024): rwlock.cpp(349): Please ignore the previous error from SQL. It is benign. ERR: MMS(4024): sql.cpp(5671): Query ({call mms_addcsobjwithpartition(?,?,?,?,?,?,?)}) performed with error ERR: MMS(4024): sql.cpp(5724): Cannot insert duplicate key row in object 'dbo.mms_connectorspace' with unique index 'IX_mms_connectorspacepobject_idrdnma_id'. ERR: MMS(4024): sql.cpp(5732): hrError: 0x80040e2f, dwMinor: 2601 ERR: MMS(4024): sql.cpp(5887): SQL error: 23000, native: 2601 BAIL: MMS(4024): sql.cpp(7381): 0x80040e2f BAIL: MMS(4024): sql.cpp(7185): 0x80040e2f ERR: MMS(4024): sproc.cpp(523): Please ignore the previous error. The error is benign. BAIL: MMS(4024): sproc.cpp(525): 0x8023040f (The object already exists) BAIL: MMS(4024): csobj.cpp(14187): 0x8023040f (The object already exists) BAIL: MMS(4024): nscsimp.cpp(440): 0x8023040f (The object already exists) BAIL: MMS(4024): syncstage.cpp(798): 0x8023040f (The object already exists) BAIL: MMS(4024): syncstage.cpp(1681): 0x8023040f (The object already exists) BAIL: MMS(4024): syncstage.cpp(288): 0x8023040f (The object already exists) ERR: MMS(4024): syncstage.cpp(337): 0x8023040f - staging failed 0x8023040f ERR: MMS(4024): syncstage.cpp(338): Staging failed 0x8023040f: [CN=******,O=person]ERR: MMS(4024): syncmonitor.cpp(2515): SE: Rollback SQL transaction for: 0x8023040f MMS(4024): SE: CS image begin MMS(4024): SE: CS image end Thank you.

Thanks for the feedback Craig. This is a production environment; however, we ended up filtering the user object from FIM's view and that did allow us to get a successful Full Import.

If this is a prod machine then I'd probably call CSS. If this is a dev/test machine then I'd clear the CS and try again in order to get a repro. It seems like an issue creating an object that the sync engine thinks exists already. You can probably find more evidence of it by dumping the CS with csexport.exe.CraigMartin Edgile, Inc. http://identitytrench.com