Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Originally Published: 2007-12-27
Article Number
Applies To
Apache Tomcat 5.5.x
Issue
Cause
use.container.credentials=true
Resolution
If setting use.container.credentials to false does not eliminate the null logins, add automaticTestTable="rkmtesttable" to both connection pools specified in kms.xml.
Notes
Related Articles
RSA Identity Governance & Lifecycle fails to start with "Connection is not associated with a managed connection" message 92Number of Views When terminating a user, the associated GoogleApps account is not disabled in RSA Identity Governance & Lifecycle 19Number of Views Remove groups from multiple disabled Accounts fails with error: "Expected 1 account associated with the ChangeRequestItem.… 81Number of Views RSA Identity Governance and Lifecycle NullPointerException when rules associated with Attribute Synchronization run 162Number of Views RSA Identity Governance and Lifecycle user account table control type in the request form does not list all accounts when … 33Number of Views
Trending Articles
Authentication Manager Log Messages (23001-23091) RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog Troubleshooting RSA MFA Agent for Microsoft Windows Customizing the Self-Service Console User Help
Don't see what you're looking for?