000022780 - Installed RSA Federated Identity Manager (FIM) as a local user with admin rights  but services do not install properly

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000022780
Applies ToRSA Federated Identity Manager (FIM) 2.6
Microsoft Windows Server 2003
IssueInstalled RSA Federated Identity Manager (FIM) as a local user with admin rights, but services do not install properly 
Microsoft Windows services used with RSA Federated Identity Manager (FIM) terminate with "Incorrect function" error message 
RSA Federated Identity Manager (FIM) works when running as an application 
ResolutionAs a workaround, you must perform a complete uninstall and reinstall of the RSA Federated Identity Manager (FIM) services using the instructions below:

1. If running, close the FIM application windows

2. Open a command prompt window and change to the following directory:


3. Once in the bin directory, type the following command:

    configtool UNINSTALLSERVICE managed

4. Again, at the command prompt, type:

    configtool UNINSTALLSERVICE admin

5. At this point, both services should now be uninstalled - to confirm, go into the Windows Services to ensure you do not see the FIM Admin or Managed services. If you do, press the F5 key to refresh the services window; these services should now disappear from the list. In some cases, a reboot may be necessary.

We will now re-add the FIM services:

6. In that same directory in step 2, type:

    configtool INSTALLSERVICE

7. When the "systempassword>" prompt appears, type the system password (this is the same password used when installing FIM)

8. At the "servertype>" prompt, type "admin" - now you should see "RSA FIM Admin Server installed..."

9. Perform the same steps starting with step 6, but instead of using "admin" in step 8, use the word "managed". Now you should see "RSA FIM Managed Server installed..."

10. Lastly, reboot the FIM Server and the services should now start correctly
Legacy Article IDa30318