EVENT ID 6311
Log Name: Application Source: FIMSynchronizationService Date: 5/15/2012 11:32:34 AM Event ID: 6311 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: <computer name> Description: The server encountered an unexpected error while performing a callback operation. "ERR: MMS(2424): obsoletionlist.cpp(319): 0 is not a valid DN depth BAIL: MMS(2424): obsoletionlist.cpp(321): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): obsoletionlist.cpp(767): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): obsoletionlist.cpp(1146): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): syncimport.cpp(804): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): syncimport.cpp(110): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): ma.cpp(4461): 0x80070057 (The parameter is incorrect.) Forefront Identity Manager 4.0.3606.2"
Log Name: Application Source: FIMSynchronizationService Date: 5/15/2012 11:32:34 AM Event ID: 6311 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: <computer name> Description: The server encountered an unexpected error while performing a callback operation.
"ERR: MMS(2424): obsoletionlist.cpp(319): 0 is not a valid DN depth BAIL: MMS(2424): obsoletionlist.cpp(321): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): obsoletionlist.cpp(767): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): obsoletionlist.cpp(1146): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): syncimport.cpp(804): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): syncimport.cpp(110): 0x80070057 (The parameter is incorrect.) BAIL: MMS(2424): ma.cpp(4461): 0x80070057 (The parameter is incorrect.) Forefront Identity Manager 4.0.3606.2"
EVENT ID 6401 (The Parameter is Incorrect)
Log Name: Application Source: FIMSynchronizationService Date: 5/15/2012 11:32:34 AM Event ID: 6401 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: <computer name> Description: The management agent controller encountered an unexpected error. "BAIL: MMS(2424): cntrler.cpp(1852): 0x80070057 (The parameter is incorrect.) Forefront Identity Manager 4.0.3606.2"
Log Name: Application Source: FIMSynchronizationService Date: 5/15/2012 11:32:34 AM Event ID: 6401 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: <computer name> Description: The management agent controller encountered an unexpected error.
"BAIL: MMS(2424): cntrler.cpp(1852): 0x80070057 (The parameter is incorrect.) Forefront Identity Manager 4.0.3606.2"
EVENT ID 6401 (Unusual Error Code)
Log Name: Application Source: FIMSynchronizationService Date: 5/15/2012 11:32:34 AM Event ID: 6401 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: <computer name> Description: The management agent controller encountered an unexpected error. "ERR: MMS(2424): libutils.cpp(10359): Unusual error code reported 0x80070057 Forefront Identity Manager 4.0.3606.2"
"ERR: MMS(2424): libutils.cpp(10359): Unusual error code reported 0x80070057 Forefront Identity Manager 4.0.3606.2"
There's a hotfix rollup package (build 4.0.3627.2) available that solves this problem (KB2737503). A hotfix rollup package (build 4.0.3627.2) is available for Forefront Identity Manager 2010
Henrik Nilsson [MVP] edited Revision 9. Comment: Chenged resolution now that there's a hotfix available.
Richard Mueller edited Revision 7. Comment: Fixed <a name> tags in HTML so TOC works
Richard Mueller edited Revision 5. Comment: Minor typo
Tim Macaulay edited Revision 3. Comment: removed the link for the hotfix download
Thanks for the post... I just hit this problem on a FlatFile MA.
A reboot of the server didnt seem to help.... but stopping and then restarting the FIM Sync Service seems to have.
Do you know if a patch is coming soon , or is it something I did that I need to avoid doing?
Hi Rob8765...
This is an on-going investigation at the moment. Stopping and Starting the Synchronization Service is probably the best way to get you past it. As soon as a fix or resolution comes about, I will be posting it.
Thank you,
Tim (timmac@microsoft.com)
I've been able to reproduce this issue!
I started getting this error when I enabled the full farm level backups using "Backup-SPFarm". I started running "Backup-SPFarm" nightly (9PM) full backup last week and started getting Event ID 6126 and 6127 when the incremental profile sync runs at 1 AM. Then I run a full sync and get the series of errors documented in this article.
I then run the full UPS sync a couple of times and the problem seems to go away until the full farm backup is run again. I know the Backup-SPFarm re-provisions (stops and starts both FIM services) as part of the backup. I believe this is causing this issue. At least it is for us.
We're running SharePoint 2010 SP1 (Feb-Mar 2012 CU).
Thanks!
I got the same error using a SQL Agent with Stage Full Profile
Hope for a patch soon
Thanks
Edi
I too got the same problem when running SAP agent , the solution worked really great, but this problem is now frequent, i have to manually stop and start the service after the agent getting failed. every time, is this comman after upgrading to R2
This error occurs on "stand alone synch servers" as well but is not solved by restarting services or even rebooting the server. I have SQL 2008 and Lotus Notes MAs that hang during export and generate this message when I attempt to stop the MA. A Server reboot is then required to continue running the other MAs on the Synch servers. These MAs have been running under MIIs and ILM FP1 for 8 years and were never a problem until we migrated to FIM2010.
Yeah is good !!