##DRAFT IN PROGRESS###

Case

FIM 2010 R2 service installation fails when connecting to remote SQL 2008 R2 SP2 server

Reference Infrastructure

FIM Test Server
- Windows Server 2008 R2
- FIM 2010 R2 installation media (also tested FIM 2010 R2 eval download)

SQL Server (other than FIM server)
- SQL Server 2008 R2 SP2

Symptoms

During setup, the wizard is able to connect to the SQL Server 2008 R2 SP2 server, and is able to create the FIMService DB.
To connect to the SQL server, the SQL server name needed to be suffixed with the ",1433" port reference.
Without the port reference the installation wizard throws an error and cannot connect to SQL.

But at the very end of the installation, you get a service start failure and the wizard then rolls back the setup.

Error message

When installing the FIM service the installation throws an error at the very end of the setup, while attempting to start the FIM Service:

Text message:
Service ‘Forefront Identity Manager Service’ (FIMService) failed to start. Verify that you have sufficient previleges to start system services.

Eventviewer

Application log on \\SERVERNAME:

[XXX] Microsoft Resource Management Service

Type: ERROR

Computer: SERVERNAME.SUBDOMAIN.LOCALDOMAIN.be

Time: dd/mm/yyyy h:MM:ss PM ID: 0

Service cannot be started. System.UriFormatException: Invalid URI: The hostname could not be parsed. at Microsoft.ResourceManagement.Service.Application.Start() at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

[750] Microsoft.ResourceManagement.ServiceHealthSource

Type: ERROR

Computer: SERVERNAME.SUBDOMAIN.LOCALDOMAIN.be

Time: dd/mm/yyyy h:MM:ss PM PM ID: 2

The Forefront Identity Manager Service could not bind to its endpoints. This failure prevents clients from communicating with the Web services. A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint. Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints. Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints. Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints.

[749] Microsoft Resource Management Service

Type: ERROR

Computer: SERVERNAME.SUBDOMAIN.LOCALDOMAIN.be

Time: dd/mm/yyyy h:MM:ss PM ID: 0

FIM Service files & config files

During installation (before roll back) the FIM Service configuration files are in place and can be checked.

But when the roll back starts, the wizard removes the files.
At rollback it's not possible to check the FIM service configuration any more.

Firewall ports

Background info

SQL Server 2008 R2 (no SP)

The FIM 2010 (R2) Service had trouble connecting to SQL Server 2008 R2 SP2, but the install wizard succeeds connecting to a SQL Server 2008 R2 instance (no SP).

We did not test SQL 2008 SP1 (as the production server had SP2).