TROUBLESHOOTING: FIM 2010 Update 2 Fails Immediately - DetectServiceAccount

TROUBLESHOOTING: FIM 2010 Update 2 Fails Immediately - DetectServiceAccount

 

PROBLEM STATEMENT

You are attempting to install Update 2 for FIM 2010 for the FIM Service and it immediately goes to the last page with no error message.  The installation screen states that the install finished prematurely.

You capture a Windows Installer Verbose log file of the installation.  In the log file, you find the following information as to why it failed.  You will see DetectServiceAccount.  This indicates that the installation is failing while firing the DetectServiceAccount Custom Action. 

Windows Installer Verbose Log File Information

MSI (c) (80:0C) [13:08:03:552]: Invoking remote custom action. DLL: %userprofile%\AppData\Local\Temp\2\MSI762F.tmp, Entrypoint: DetectServiceAccount

CustomAction DetectServiceAccount returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (c) (80:0C) [13:08:03:649]: Closing MSIHANDLE (4) of type 790542 for thread 3360

Action ended 13:08:03: DetectServiceAccount. Return value 3.

 

CAUSE

The service is running with a UPN logon rather than DOMAIN\UserName.

RESOLUTION

  1. On the FIM Service Machine, open the Services.mmc
  2. Find the Forefront Identity Manager Service and open the properties
  3. Select Logon Tab
  4. Replace the UPN information with a DOMAIN\UserName format
  5. Click Ok
  6. Restart the Forefront Identity Manager Service
  7. Execute the installation

 

SEE ALSO

Leave a Comment
  • Please add 8 and 4 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Richard Mueller edited Revision 2. Comment: Removed (en-US) from title, modified title casing, added tags

  • Tim Macaulay edited Revision 1. Comment: fixed the links

Page 1 of 1 (2 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Richard Mueller edited Revision 2. Comment: Removed (en-US) from title, modified title casing, added tags

  • I was not doing trying to do the Update 2 to FIM 2010, but I was trying to run the Synchronization Service Manager and got the error below.

    "Unable to connect to the Synchronization Service.

    Some possible reasons are:

    1) The service is not started

    2) Your account is not a member of the required security group."

    But change the UPN information to DOMAIN\UserName format worked perfectly for me.

    Thanks

  • Tim Macaulay edited Revision 1. Comment: fixed the links

Page 1 of 1 (3 items)