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
When terminating a user, the associated GoogleApps account is not disabled in RSA Identity Governance & Lifecycle Number of Views RSA Identity Governance & Lifecycle fails to start with "Connection is not associated with a managed connection" message Number of Views RSA Identity Governance and Lifecycle user account table control type in the request form does not list all accounts when … Number of Views Remove groups from multiple disabled Accounts fails with error: "Expected 1 account associated with the ChangeRequestItem.… Number of Views Access User Access Review not showing indirect entitlements associated with a role for RSA Identity Governance & Lifecycle… Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
