Debugging configtool problems in RSA Federated Identity Manager (FIM) 2.5
Originally Published: 2005-01-11
Article Number
Applies To
Microsoft Windows 2000 Server SP4
Issue
Error executing: UPDATEVERSIONPATCH
The administration server could not be contacted
Cause
Resolution
1. The error message itself may be enough to identify the issue
2. A log file showing a history of configtool commands may be reviewed; this log file is located at <INSTALLDIR>\log\configtoolhistory.log
3. Debugging may be enabled on configtool for expanded debugging. To enable debugging, modify the <INSTALLDIR>\bin\setenv.cmd file by finding the line (very near the end):
set LOG4J_CONFIG=file:%PROPERTIES_DIR%\DisableAuditLogConfig.properties
and replace it with the following:
set LOG4J_CONFIG=file:%PROPERTIES_DIR%\DebugAuditLogConfig.xml
This will now generate debug output in <INSTALLDIR>\log\debug.log
NOTE: Remember to change the setenv.cmd file back after you have finished debugging
Related Articles
Error: Error 'Socket Closed exception in RSA Federated Identity Manager (FIM) 2.5' Number of Views RSA Federated Identity Manager 4.2 SP1 class loading install issue with fim.jar and deployment script Number of Views Error: 'Relying Party servlet: java.lang.NullPointerException' in RSA Federated Identity Manager (FIM) Number of Views Debugging configtool problems in RSA Mobile 1.5 Number of Views Error: 'The server has not found anything matching the Request-URI' in RSA Federated Identity Manager (FIM) Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
