000025915 - Debugging configtool problems in RSA Federated Identity Manager (FIM) 2.5

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 Number000025915
Applies ToRSA Federated Identity Manager (FIM) 2.5
Microsoft Windows 2000 Server SP4
IssueDebugging configtool problems in RSA Federated Identity Manager (FIM) 2.5
The administration server could not be contacted
CauseVarious issues may arise, meaning the configtool utility will fail with a variety of error messages (two sample messages are shown here)
ResolutionThere are 3 levels of diagnosis to resolve problems with configtool:

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
Legacy Article IDa24511