All 1 entries tagged Fimservice
No other Warwick Blogs use the tag Fimservice on entries | View entries tagged Fimservice at Technorati | There are no images tagged Fimservice on this blog
October 04, 2013
The FIM Service needs an internet connection to complete installation. If you use a FIM development or sandbox environment that is isolated from your main network and the Internet, you may find the FIM Service will not start at the end of the installation process, and fails with a timeout error.
The issue is caused because the default timout for a service to start-up is 30seconds. The FIM Service uses the .NET 3 framework, and at FIM Service startup the .NET CLR attempts to validate the .NET authenticode signature by connecting to a microsoft web-site. If you have no connection to the Internet the authenticode certificate revocation check will wait for several minutes before timing out, by which time the FIM service-startup has timed-out.
I resolved the problem by configuring an additional temporary network interface to my VM which natted to my real network. Once the VM could 'see' the Internet to do the signature check, the FIM Service started normally. Then I removed my temporary network interface.
You could also:
- increase the timeout delay for starting services
- reconfigure your Microsoft.ResourceManagement.Service.exe.config file to remove the revocation check altogether
(FIM service fails to start. Fim service does not start. Fim installation fails)