'java.sql.SQLException invalid object name userbase' When Integrating with JIRA for User Management
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
When using Delegate user management to use JIRA logins, 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:
1
2
3
4
5
6
7
8
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.
Solution
Resolution
Change the schema in SQL Server to match the settings in server.xml and entityengines.xml.
Was this helpful?