All, An issue has recently popped up in support. We have documented it on the following TechNet Wiki TROUBLESHOOTING: stopped-server (Event ID: 6311 and 6401): http://social.technet.microsoft.com/wiki/contents/articles/10930.troubleshooting-stopped-server-event-id-6311-and-6401.aspx Let me know if you have any questions. Tim (timmac@microsoft.com)Timothy P Macaulay Security Identity Support Team at Microsoft timmac@microsoft.com

Im having this problem with a SQL Server MA, every time I run a Full Import or a FIFS it bombs with this error. Yesterday I restarted the services as mentioned and it appeared to fix the problem. Today I dont appear to be so lucky, several service restarts and server reboots and the problem persists. I noticed this mentioned at the bottom of the wiki. Another possible item to check, is for any failed .NET Updates ( patches ) that may have happend during a Windows Update Services install What do you mean check for failed .NET Updates?. Were using Win2008 R2 SP1(64bit) and FIM 2010 R2 Version: 4.1.2273.0.

I'm having the same issue at a customer site with the FIM Service MA. After a sync service restart, I can do one full sync. After that, I get the stopped-server error. The delta sycs and exports still run fine. I have tried some of the PowerShell scripts to verify the account SID and everything looks fine. This customer is on: FIM version 4.0.3606.2 Thanks, Mark Mark Creekmore - BlueVault Software http://www.bluevaultsoftware.com

OK - maybe not related but I've got same problem with AD MA - cause as suggested by someone on this forum was change in AD schema. As I'm saying - it might be not related, but refreshing the schema on MA won't take long and will not cause more problems :).

Well, it was worth a try. It didn't seem to help anything. Thanks for the suggestion. MarkMark Creekmore - BlueVault Software http://www.bluevaultsoftware.com

I am having this issue with SQL MA's. Restarting services as advised in the blog doesn't help at all. We updated up to 4.0.3617.2 with no help. All schema's have been refreshed and updated with no help. I've got a case opened, but so far nothing has helped.

All, There appears to be something wrong with this update 2. I just recently updated to version 4.0.3606.2 to address some AD Recycle Bin issues and I am seeing the same issues. In my case, the issue is occurring on a file-based MA. I only do a Full Import and Full Synchronization from this MA since day one. When I start the run profile I noticed that the MA is reporting Full Import and Delta Synchronization. I went into the run profile, created a new step and removed the old one. I also restarted the Sync service for good measure. This allowed me to run the expected Full Import and Full Synchronization once and then it reverted back to trying a delta. fr3dd

in our case we deleted the MA and rebuilt it from scratch. the problem seems to be fixed.

Hotfix 4.1.3627.2 fixed our issue. Ask your PSS for it. KB2737503