'java.sql.SQLException invalid object name userbase' When Integrating with JIRA for User Management
Symptoms
When using JIRA for User Management, the database connection fails and users cannot log into Confluence. This often happens after a database migration to a new system.
The following appears in the atlassian-confluence.log:
2011-01-24 13:46:47,832 FATAL [http-8090-8] [user.provider.jdbc.JDBCCredentialsProvider] handles Could not see if [admin] is handled
-- url: /dashboard.action | userName: anonymous | action: dashboard
java.sql.SQLException: Invalid object name 'userbase'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
Diagnosis
- In JIRA, check
atlassian-jira/WEB-INF/classes/entityengines.xml. Note the schema name. It is likely 'jiraschema'. - In Confluence, check
conf/server.xml. Notice the schema name. - In SQL Server, check the schema name. It may be 'dbo' or other.
Cause
The schema names are inconsistent.
Resolution
Change the schema in SQL Server to match the settings in server.xml and entityengines.xml.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.