Hi, On a few occasions now we've had an issue where the FIMService stops and cannot be restarted. A pop up box appears on the screen indicating that the FIM Service has a dependant service missing and is marked for deletion. Inspecting the dependency tab in services reveals no dependent services, however, in the registry a dependent service key appears under HKLM\SYSTEM\CurrentControlSet\Services\FIMService. This key shows a service with the name MSSQL$Instance_name which of course doesn't exist locally as SQL is installed remotely. This key is not present on a working system. Any ideas why this should appear or the FIMService should fall over like this?? Rob

Hi Rob, I've encountered this multiple times now and have just documented it here: http://www.identitychaos.com/2010/04/fimservice-dependency-service-does-not.html To resolve this: sc.exe \\server config FIMService depend= / Any help reproducing this would go a long way towards fixing the issue in a future update. In my case I have: Two backend SQL Servers, multi-instance (separating out FIMSync db from FIMService db) Two web/app frontend servers running WSS in Web Farm mode Web node 1 has all of the FIM Portal and Service options installed (not exhibiting the problem) Web node 2 has only the FIM Service installed (exhibited this problem) SQL node 1 has FIM Service installed, and therfore the dependency is valid WSS SP2 with the Feb CU I'm pretty sure I've seen this on multiple frontends in the past and without the Feb CU for WSS. I also made sure that I'm not running the Windows Internal Database on the frontends. Only the SQL Tools are installed on the web frontends per the prerequisites.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

Filed on connect as: https://connect.microsoft.com/site433/feedback/details/549068/rtm-fim-service-registers-mssql-dependency-incorrectlyBrad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com