Contents
What to do if your FIM service does not start?
The SQL administrator took swift action and simply moved the FIM Service DB to another LUN. He let the FIM Administrator know and the FIM Admin began double-checking his FIM environment. He noted that he was unable to get into the Portal and worse, the Portal would not even start.
How to troubleshoot the FIM service in SQL?
To resolve the issue, we followed these steps: 1 Open SQL Management Studio 2 Connect to the instance of SQL that contains the FIM Service DB 3 Right-click on the FIM Service DB 4 Select Properties 5 Click on Options 6 Scroll down to Service Broker 7 Changed Broker Enabled from “False” to “True” More
Why is my Forefront Identity Manager not starting?
“windows could not start the forefront identity manager >synchronization service on local computer. for more >information, review the system event log. if this is a non->microsoft service contact the service vendor, and refers to >service specific error code -2146234334”
Is there a disconnect between SQL and FIM?
Many times, a disconnect between the SQL administrators and FIM administrators can develop; one such disconnect occurred today. The SQL administrator noted that the FIM administrators SQL DB was filling up most of the drive and was beginning to throw warnings to the system administrators.
Is there a script to start the synchronization serivice?
If anyone is interested, i created a script that cleans up and starts the Synchronization serivice for you: http://sharepointbjorn.com/2014/06/25/user-profile-synchronization-autofixer/
Do you need to input farm PWD when starting the synchronization service?
Restarts the user profile instance and starts the Synchronization service, you will need to input farm pwd when it asks for it. You run it on the server hosting the synchronization service. It targets the local server. Setting FIM Services to “Local System” not fix the problem.