Table of Contents


Shortly after the "deploying solution packs" step of the installer for the FIM Service and Portal, the installation rolls back without warning or error.  Verbose logging of the install showed the following information preceding a 'return value 3.'


MSI (s) (1C!3C) [13:05:32:956]: Closing MSIHANDLE (179) of type 790531 for thread 4668

MSI (s) (1C!3C) [13:05:33:034]: Creating MSIHANDLE (180) of type 790531 for thread 4668

CAQuietExec:  An exception occurred while running Microsoft.IdentityManagement.SolutionPackUtility.exe: The Web site address "/IdentityManagement" is already in use.


Action 11:21:30: InstallCommonPortal. Deploying solution packs
MSI (s) (7C:1C) [11:21:30:454]: Executing op: CustomActionSchedule(Action=InstallCommonPortal,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData="E:\Program Files\Microsoft Forefront Identity Manager\2010\Portal\Microsoft.IdentityManagement.SolutionPackUtility.exe" action=Install mode=ServiceAndPortal log=event SHAREPOINTTIMEOUT=180 SolutionPack=MicrosoftILMPortalCommonDlls.wsp UILevel=5)
MSI (s) (7C:50) [11:21:30:500]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIFACB.tmp, Entrypoint: CAQuietExec
CAQuietExec: Microsoft.IdentityManagement.SolutionPackUtility.exe will deploy and/or retract the FIM solution packs. This operation may take long time in a SharePoint farm environment.
CAQuietExec: Executing all administrative timer jobs in preparation for FIM solution pack deployment.
CAQuietExec: An exception occurred while deploying/retracting FIM Portal solution packs. Exception : Exception has been thrown by the target of an invocation.
CAQuietExec: Error 0xfffffff9: Command line returned an error.
CAQuietExec: Error 0xfffffff9: CAQuietExec Failed
CustomAction InstallCommonPortal returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)


The user performing the install does not have sufficient SharePoint privileges to modify the FIM Portal web site address.  Specifically, the install account was a member of SharePoint Farm Administrators, but not Site collection Administrators.


Adding the install account to the Site Collection Administrators group in SharePoint and performing an IISRESET allowed the installer to complete successfully.