FIM R2 SP1: FIM Service and Portal Setup Wizard ended prematurely :'( RRS feed

  • Question

  • Hey everyone, I'm trying to install FIM for a customer's lab and I have run into a problem.

    Everytime I try to install the Service & Portal, the installation simply ends saying that the FIM Wizard ended prematurely. It doesn't tell me why or what went wrong.

    To give you a little background on the environment, the FIM Sync machine is running Windows Server 2008 and already has FIM R2 SP1 installed with its own SQL 2008.

    There is another machine running Windows Server 2012 which is also running SQL 2012. This is the SQL that the Service and Portal should be using.

    Finally, there is the Service & Portal machine. It is running on Windows Server 2012 as well as SharePoint 2013.

    Of course, there are other machines such as the Domain Controller and Exchange but I doubt there is anything wrong with those machines.

    Since the error is so vague, I ran a log file with Verbose to see what the problem could be. This is the last few lines before the log file ended. I cant post it all since it is too long but if there are other parts of the log you want, just let me know.

    Property(C): CAN_CONNECT_TO_SQL_SERVER = 1
    Property(C): IS_VALID_DATABASE_NAME = 1
    Property(C): IS_VALID_DOTNET_VERSION = 1
    Property(C): IS_SYNC_SERVICE_RUNNING = 1
    Property(C): IS_SYNC_SERVICE_EXISTS = 1
    Property(C): IS_SQL_AGENT_RUNNING = 1
    Property(C): SQLAGENTEXIST = 1
    === Logging stopped: 5/6/2013  10:11:50 ===
    MSI (c) (7C:84) [10:11:50:327]: Note: 1: 1708 
    MSI (c) (7C:84) [10:11:50:327]: Product: Forefront Identity Manager Service and Portal -- Installation failed.
    MSI (c) (7C:84) [10:11:50:327]: Windows Installer installed the product. Product Name: Forefront Identity Manager Service and Portal. Product Version: 4.1.3419.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    MSI (c) (7C:84) [10:11:50:327]: Grabbed execution mutex.
    MSI (c) (7C:84) [10:11:50:327]: Cleaning up uninstalled install packages, if any exist
    MSI (c) (7C:84) [10:11:50:327]: MainEngineThread is returning 1603

    If anyone knows what the problem could be or what can make it work, it would be GREATLY appreciated.

    Thank you!

    Monday, May 6, 2013 2:41 PM

All replies

  • The actual failure is going to be earlier in the log.

    My Book - Active Directory, 4th Edition
    My Blog -

    Monday, May 6, 2013 3:36 PM
  • Do you know how much earlier by any chance? The log is 75 pages long if I put it into a word document.

    Monday, May 6, 2013 3:47 PM
  • Do you know how much earlier by any chance? The log is 75 pages long if I put it into a word document.

    No. You're going to have to run through it and see what sticks out to you.

    My Book - Active Directory, 4th Edition
    My Blog -

    Monday, May 6, 2013 4:11 PM
  • I read it and I did find an exception was thrown. It seems to have to do with SharePoint but I went to the SharePoint site and it seems to work correctly. What do you think the problem could be. I am not to familiar with the new version of SharePoint. The exception is as follows:

    Calling custom action Microsoft.IdentityManagement.SharePointCustomActions!Microsoft.IdentityManagement.ManagedCustomActions.SharepointCustomActions.VerifyClaimsAuthenticationOff  

    Property name = 'SHAREPOINT_URL', value = 'http://IDM-FIM-115'.

    Exception thrown by custom action:

    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: The Web application at http://IDM-FIM-115 could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

       at Microsoft.SharePoint.SPSite.LookupSiteInfo(SPFarm farm, Boolean contextSite, Boolean swapSchemeForPathBasedSites, Uri& requestUri, Boolean& lookupRequiredContext, Guid& applicationId, Guid& contentDatabaseId, Guid& siteId, Guid& siteSubscriptionId, SPUrlZone& zone, String& serverRelativeUrl, Boolean& hostHeaderIsSiteName, Boolean& appWebRequest, String& appHostHeaderRedirectDomain, String& appSiteDomainPrefix, String& subscriptionName, String& appSiteDomainId, Uri& primaryUri)

       at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, Boolean swapSchemeForPathBasedSites, SPUserToken userToken)

       at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)

       at Microsoft.SharePoint.SPSite..ctor(String requestUrl)


       at Microsoft.IdentityManagement.ManagedCustomActions.SharepointCustomActions.VerifyClaimsAuthenticationOff(Session session)

       --- End of inner exception stack trace ---

    Monday, May 6, 2013 4:42 PM
  • Is that the hostname of the local server or a different machine?

    My Book - Active Directory, 4th Edition
    My Blog -

    Monday, May 6, 2013 4:45 PM
  • It's the local server where SharePoint 2013 is currently installed and where I am now trying to install the Service & Portal
    Monday, May 6, 2013 4:49 PM
  • Two things:

    1. There's specific guidance on TechNet around FIM + SharePoint 2013. Make sure you have reviewed that

    2. Try using localhost instead of the hostname.

    My Book - Active Directory, 4th Edition
    My Blog -

    Monday, May 6, 2013 4:50 PM
  • I'll also note that the FIM Portal installer is very fussy about the Sharepoint Alternate Access Mappings.  Even though you may be able to browse the site with a variety of hostnames, the FIM installer will fail if it doesn't line up exactly with an AAM.

    Steve Kradel, Zetetic LLC

    Monday, May 6, 2013 8:29 PM
  • Did you use another account to install sharepoint?

    Also make sure the user you are installing FIM from is also a site administrator in SharePoint.

    Also check that the Web Application Sharepoint-80 is present and you can access it using http://localhost

    Finally if it is in the same machine and as brian suggested you should use http://localhost during the setup.

    Regards Furqan Asghar

    Tuesday, May 7, 2013 8:44 AM
  • Seriously, save yourself some trouble... uninstall SharePoint Foundation 2013 and use WSS 3.0 or SharePoint Foundation 2010.

    That said, if you're running Windows Server 2012, you HAVE to use it.. if you simply HAVE to use it, then read my guide:

    Installing FIM 2010 Portal on SharePoint Foundation 2013

    If I were to guess.. I would say you have used the default install + configuration within SPF 2013, which sets your site up in such a way that it will not be compatible with FIM. I repeat, the default installation & configuration settings for SPF 2013 will not work for FIM.

    Then go read Spencer Harbar's guide, which is really in-depth.

    - Ross Currie | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    Wednesday, May 8, 2013 3:38 PM
  • I finally got it to work. The problem was with the ports. When we first created it, we used port 8080. After it was competed, we switched it to port 80 but it seemed we didn't change it everywhere which is why FIM kept getting confused. We changed everything back to port 8080 and FIM was able to install without a hitch.

    Thanks everyone for all their help


    • Proposed as answer by Ross Currie Wednesday, May 8, 2013 4:30 PM
    Wednesday, May 8, 2013 4:27 PM
  • I think we're going to have to start compiling a list of errors that lead to the "installation ended prematurely error". There do seem to be a few common themes.

    - Ross Currie | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    Wednesday, May 8, 2013 4:30 PM