RSA Federated Identity Manager (FIM) services do not start after changing hardware (upgrading RAM etc.) to the machine running FIM
Originally Published: 2006-06-08
Article Number
Applies To
RSA Mobile 1.5
Microsoft Windows Server 2003 SP1
Issue
RSA Federated Identity Manager (FIM) issue upgrading the physical memory
Error: "Debug assertion failed" while starting service in RSA Federated Identity Manager (FIM)
Error: "_BLOCK_TYPE_IS_VALID" while starting service in RSA Federated Identity Manager (FIM)
Resolution
ram_info
os_version
mac_address
machine_name
disk_serial_number
diskcontroller_id
cpu_id
Therefore, if any of the above changes, you must uninstall and reinstall the FIM service to ensure that a new encryption key is generated. Refer to the FIM documentation for an explanation on how to uninstall and reinstall FIM services.
Related Articles
SOM Web Form Matching Number of Views RSA Token Client (RTS) DLL not rotating its log file Number of Views Security Object Manager (SOM) client fails to connect to SOM Server Number of Views Can a certificate be imported onto SID800 using RSA Smart Card Middleware 3.0 ? Number of Views How to recreate a PKCS#12 and/or to change PKCS#12 password? Number of Views
Trending Articles
AFX Server remains in a 'Not running' State, afx status shows 'timed out waiting for AFX applications to start' and mule_e… RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.7 SP1 Patch 1 Hotfix 1 RESTful Web Service Connector capability test fails with unauthorized (401) error when using Basic authentication in RSA G… RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide
Don't see what you're looking for?
