Recently I have been working with several customer that experienced a similar situation:
- update FIM with a hotfix fails
- upgrade FIM 2010 to FIM 2010 R2 fails
- during installation of FIM he FIM services won’t start
All of them result in a roll-back of the installation.
Let me spoil the root cause right away (and then explain): using an SQL port number in the installation wizard.
The installation wizard is not able to connect to the database with a port number.
Solution: use an SQL alias
The FIM Sync Service and/or the FIM servers check the registry for the database server and instance and then connect to SQL and start the service.
The use of a port number seems to break the wizard.
Normally the FIM Services and FIM Sync Services CAN use an SQL port…
Easy fix: set an alias in the SQL Server client network utility
Then change the registry to use the FIM SQL ALIAS (as server), you don’t need the instance and port anymore (as the alias will take care of it).
For the FIM Sync:
Check the server and instance configured for the FIM Sync database
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters\Server (use SQL Alias)
for FIM Service
Check the server and instance configured for the FIM Service database
I’ve updated the Wiki article with more detailed info at http://social.technet.microsoft.com/wiki/contents/articles/14551.fim-2010-r2-troubleshooting-syncservice-installation-or-upgrade-failure-and-roll-back.aspx