Time to hit the forums... maybe you guys can help I've setup FIM 2010 R2 in the following way: FIM Service + FIM Portal + SSPR Portals on 2 physical servers configured in NLB. FIM Sync + SQL 2008 hosting all DB's on SQL Cluster The services was configured, and setup correctly. All Identities imported into the portal and UAT started on Password Self Service. Everything was working 100% for the last 3 weeks now. This morning I tried registering for password reset using a test user, I got service unavailable in the portal. Went to check that the FIM Service is running, and sure enough, on NLB Bode 1 the service is running 100%, but on NLB 2, the FIM Service was not running. Trying to start the service resulted in the normal windows error 1053 "the service did not respond in a timely fashion" with event viewer errors: 1. Event ID 7009 A timeout was reached (30000 milliseconds) while waiting for the Forefront Identity Manager Service service to connect 2. Event ID 7000 The Forefront Identity Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. I've restarted the server several times, I've enabled advanced logging in the "Microsoft.ResourceManagement.Service.exe.config" file and tried to start the service, hoping in some sort of error logging in the log files... But nothing, nothing in the event viewer and no log files generated. My question, if node one is starting 100% with same accounts as node 2, but node 2 doesn't want to start... where do I start looking, how do I enable some sort of logging so I can at least try and troubleshoot this problem... NOTE: I had this problem is the past, and the only way to resolve it in the past was to re-install the FIM service.... This time, I would like to try and figure out why this is happening... Any ideas welcome... Thx Q

Have you added any custom activities to the portal? I had a similar problem where the FIM Service crashed all the time and it turned out there was an error in a custom activity that caused the problem. Once I resolved that it worked like a charm. Good luck and let us know how it goes.

Hi, unfortunately there are no custom activities yet... only standard SSPR activities and workflows. I manage to fix the problem by reinstalling the FIM Service, like I did before... but I cant keep doing this all the time... at some point this service should go into production... If only I could enable some sort of advanced logging for service start-up...

If you don't see anything on the FIM side you might wanna check SQL. Perhaps something is off over there... Allthough one would think you would get some sql related events on the FIM box. But it's just a shot.http://setspn.blogspot.com