Today I worked on a hot fix installation issue. The installation goes through and hits a certain point, and then without warning, or error the installation rolls back. I realize that this can be a bit frustrating as to why this happens. I have come
across two different reasons that this happens. Here is documentation on one, and how I went through troubleshooting the issue.
I obtained a Windows Installer Verbose Log File through the following steps:
In reviewing the Windows Installer Verbose Log File, I searched for “Return Value 3” and found the following information.
CAQuietExec: Retracting ILMPasswordPortal.wsp
CAQuietExec:An exception occurred while running Microsoft.IdentityManagement.SolutionPackUtility.exe: A deployment or retraction is already under way for the solution "ilmpasswordportal.wsp", and only one deployment
or retraction at a time is supported.
CAQuietExec: An error occurred while retracting FIM portal solution packs.
CAQuietExec: Error 0xfffffffa: Command line returned an error.
CAQuietExec: Error 0xfffffffa: CAQuietExec Failed
CustomAction PatchRemoveFIMPWDPortal returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 15:53:06: InstallExecute. Return value 3.
CAQuietExec: Adding feature for MicrosoftILMPortalCommonDlls.wsp
CAQuietExec: An exception occurred while running Microsoft.IdentityManagement.SolutionPackUtility.exe: Feature 'MSILM2CommonWebConfiguration' (ID: 7c43ce5b-a59b-44f5-9e8a-50bd1b696145)
is already activated at scope 'http://localhost'.
CAQuietExec: An error occurred while deploying FIM portal solution packs.
Action ended 9:28:34: InstallExecute. Return value 3.
The verbose log indicated that the Microsoft.IdentityManagement.SolutionPackUtility had another deployment or retraction already started for the “ilmpasswordportal.wsp”.
To resolve this issue, I removed the “Windows SharePoint Services Solution Deployment for “Ilmpasswordportal.wsp” with the following steps:
When it appeared that the solution pack was stuck in a “deploying” state & causing the FIM timeout, and option 1 failed we executed this command on both servers prior to attempting the install again:
Open elevated command prompt cd to C:\program files\common files\microsoft shared\web server extensions\12\bin
stsadm -o execadmsvcjobs – note if your running a farm this must be run on all font end servers
This just forces any administrative timer jobs in the queue to run immediately.
SharePoint also caches a lot of information locally to reduce SQL trips, so just as a precaution we also cleared its config cache. Detailed instructions for that can be found
After trying Option 1 and Option 2 we found error in the install log referencing a feature that was already activated: An exception occurred while running Microsoft.IdentityManagement.SolutionPackUtility.exe: Feature
'MSILM2CommonWebConfiguration' (ID: 7c43ce5b-a59b-44f5-9e8a-50bd1b696145) is already activated at scope 'http://localhost'.
This indicates that when it retracted the solution during one of the failed attempts, it probably didn’t fully clean up that feature. We looked in Central Admin in the site settings and didn’t see that feature. What we needed to do next is forced the
deactivation and removal:
(notice the feature ID used in this command is the feature ID from the error message. If you encounter this again, change the feature ID as needed):