Karchworld Identity

Adventures in identity management, federation, directory services, software engineering, computer science...

Forefront Identity Manager Synchronization Service is having trouble contacting SQL server -- Bah!

Forefront Identity Manager Synchronization Service is having trouble contacting SQL server -- Bah!

  • Comments 2

When installing FIM, do you ever get one of these:

"Forefront Identity Manager Synchronization Service is having trouble contacting SQL server using the provided information. Please note that Forefront Identity Manager Synchronization Service requires Microsoft SQL Server 2008 SP1 or better. Verify the version, server and instance names as well as firewall settings and try again."

99 times out of 100, the issue turns outt hat you fat-fingered or simply have the server and instance names wrong. However, for that 1 time out of a 100, it can be frustrating to debug. I ran into the one of these times this morning and thought I'd put together a check list for the next I (or you) need it:

  1. Double check that you indeed did not fat-finger or simpy are using the wrong server and host names.
  2. Verify that you can access the server via an ODBC connection going to: Administrator Tools --> Data Sources --> User DSN tab --> Add --> Fill in the server information --> Click "Test Connection"
  3. Check the firewall rules / See if you can telnet to the server via: telnet XX.XX.XX.XX: 1433
  4. Disable IESC for Administrators if it is on
  5. Verify that Full Text Server is installed on the SQL server.
  6. Verify that SQL Agent and Browser (if you are not using the default instance) are running.
  7. Verify that the SQL Native Client is installed.

Hope this helps!

 

Comments
  • If you are using SQL 2012 make sure you are using FIM Identity Management 2010 R2 SP1 (R2 does not support SQL 2012)

  • 7.Verify that the SQL Native Client is installed. did the trick for me.

Page 1 of 1 (2 items)
Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post