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
Name resolution errors in RSA Federated Identity Manager (FIM) 2.5 Number of Views Error: 'Relying Party servlet: java.lang.NullPointerException' in RSA Federated Identity Manager (FIM) Number of Views Error: 'null; nested exception is: java.lang.NullPointerException' in RSA Federated Identity Manager (FIM) 2.5 Number of Views Error: Error 'Socket Closed exception in RSA Federated Identity Manager (FIM) 2.5' Number of Views Error message "failed to preload on startup in Web application" in RSA Federated Identity Manager (FIM) 2.5 Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA
Don't see what you're looking for?
