Debugging configtool problems in RSA Mobile 1.5
Originally Published: 2003-05-13
Article Number
Applies To
Microsoft Windows 2000
Issue
Cause
Resolution
set OPTIONS=%OPTIONS% -Dlog4j.configuration=file:%PROPERTIES_DIR%\webserverlogconfig.properties
and replace it with the following:
set OPTIONS=%OPTIONS% -Dlog4j.configuration=file:%PROPERTIES_DIR%\CSFDevAuditLogConfig.xml
This will now generate debug output inCSFDebugTrace.txt in the <root-install>/rsaapserver/bea/wlserver directory.
If when you make the change you get an "UnsatisfiedLinkerError", this may be caused by the system looking for but not finding NTEventLogAppender.dll. This file should be copied to the <root-install>/rsaapserver/bin folder; if it is present in %SYSTEM32% , copy it from there - leaving a copy in %SYSTEM32%.
Related Articles
Debugging configtool problems in RSA Federated Identity Manager (FIM) 2.5 Number of Views Demo certificates expire in RSA Mobile 1.5 Number of Views How to enable the SSO Configuration menu in the RSA Mobile Lock Console Number of Views How to change message seen by end user's mobile phone in RSA Mobile Authentication Server 1.5 Number of Views Error: 'The user is not enabled for authentication. Please contact your administrator.' in RSA Mobile Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
