FIM 2010 R2: SQL server service should be running on the remote server

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Forefront Identity Manager 2010 R2 Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer (


Forefront Identity Manager 2010 R2


FIM Service and Portal

Operating System

Windows Server 2008 R2






FIMServiceDB/FIMSyncServiceDB – SQL Server is not running on the remote server.

FIM Service DB unavailable

FIM Sync Service DB unavailable


FIMServiceDB/FIMSyncServiceDB – FIM Service (FIM Synchronization service) database scan cannot be run on the target machine.


FIMServiceDB/FIMSyncServiceDB – SQL server service should be running on the remote machine before starting a scan.

To verify that the SQL service is started, use the following procedure:

Verify that the SQL Server service is running

  1. Log on to the SQL server that is home to the FIM Service database or the FIM Synchronization service database.

  2. Click Start, select Administrative Tools, and select Services.

  3. Scroll down and ensure that SQL Server (MSSQLSERVER) has a status of Started. If not, you can right-click and select Start from the drop-down.

Additional references

For more information, see the FIM 2010 R2 Deployment Guide (