Unattended install of FIM Portal only RRS feed

  • General discussion

  • I'm looking at unattended installs for deploying the various components of FIM 2010 R2.

    I've been successful with the FIM Sync and FIM Service components, but am having problems with installing just the FIM Portal component.

    In the first instance, I'm trying to install all the components on to a single server (though the FIM Sync and FIM Service databases are on a separate server). After a few unsuccessful attempts, I managed to get the following command line to at least install the product without error:


    Performing a manual install with the information used in the command line is successful. However, after running the unattended install, when I start the Sharepoint Central Administration site, it reports a handful of errors related to the SPTimerService:

    • The server farm account should not be used for other services -- not sure why this is happening as SharePoint Foundation is set up as Standalone
    • Missing server side dependencies
    • Outbound e-mail has not been configured
    • Occasionally it also reports a problem with the STS

    Can anyone point out what I might be doing wrong?

    Steve G

    Sunday, November 4, 2012 9:11 PM

All replies

  • One thing to always check, is that you can get to the default SharePoint site before trying to install the FIM Portal. From you description it looks a as SharePoint problem more than a FIM Portal problem.

    Also, from your command line it seems that you're not using FQDN for FIM service address/url? Have you properly configured Kerberos/SPN's for service accounts as described in the "Before you begin" section on TechNet. Not sure this has anything to do with your problem here, but you should definitely try to get this sorted out as well.

    You could also try to turn on logging of MSIE using the /LV "C:\Temp\Install.log" parameter for msiexec.

    Regards, Soren Granfeldt
    blog is at | twitter at!/MrGranfeldt

    Monday, November 5, 2012 7:13 PM
  • Thanks for the reply, Søren.

    I can reach the default SharePoint site prior to install.

    The SPNs are registered as follows:

    FIM Service:

      • setspn -s FIMService/fimsvc corp\fimservice
      • setspn -s FIMService/ corp\fimservice

      FIM Portal:

      • setspn -s http/portal corp\spservice
    • setspn -s http/ corp\spservice

    I've retried the installation using an FQDN for the FIM service address, but the result is the same. The verbose logging didn't show up anything either!

    As this is a lab environment, I think I may just tear it down and start again. If the problem reoccurs, I'll post back.

    Steve G

    Tuesday, November 6, 2012 8:58 AM
  • OK, I've rebuilt the environment from scratch using manual methods and on the surface things appear to be OK, i.e. the FIM Portal now works!

    The only issue I have is some errors reported by the SharePoint Health Anayzer as shown below:

    I guess the warning about the server farm account could be ignored. The detail of the message complains about the SPUserCodeV4(Windows Service) account running under NetworkService. This is the same account as that used by the Farm account, though SPF was installed as Standalone not a farm.

    The outbound e-mail configuration I can deal with, it is just the missing server side dependencies I can't figure out. The detail of the message is as follows:

    [MissingSiteDefinition] 1 Sites in database [WSS_Content] has reference(s) to a missing site definition, Id = [10005], Lcid = [1033]. The site definitions with Id 10005 is referenced in the database [WSS_Content], but is not installed on the current farm. The missing site definition may cause upgrade to fail. Please install any solution which contains the site definition and restart upgrade if necessary.

    Can anyone point to what may be causing these issues? Prior to installing the FIM Service and FIM Portal components, the SPF Central Administration site did not record any errors. They only seem to appear after the FIM Portal component is installed.

    Steve G

    Tuesday, November 6, 2012 5:16 PM