Confluence Docs 3.0 : When setting up JIRA user management in Confluence, the Confluence login page loads with an error This page last changed on Mar 02, 2009 by jlargman. When setting up JIRA user management in Confluence, the Confluence login page loads with one of the following errors: An error is encountered when JIRA is using Microsoft SQL Server The Confluence login page loads with a 'NullPointerException' system error The Confluence login page loads with 'HTTP Status 404' and the output log shows a 'java.lang.ClassNotFoundException' error for the driver, eg 'com.mysql.jdbc.Driver' ## An error is encountered when JIRA is using Microsoft SQL Server There is a known issue when JIRA is using Microsoft SQL Server and the schema name is 'jira'. Unfortunately in Confluence, you cannot define this schema name. Please refer to Knowledge Base article CSP-19533. ## The Confluence login page loads with a 'NullPointerException' system error If the page loads with 'System error' with cause 'java.lang.NullPointerException at com.atlassian.user.impl.osuser.OSUUserManager.getOpensymphonyUser(OSUUserManager.java:85)' and output logs shows 'user.provider.jdbc.BaseJDBCProvider] init Could not look up DataSource using JNDI location' error, either the Resource for the DataSource is not being loaded by the application server, or it is being loaded but the resource names do not match. Check the names first, so if '/confluence/WEB-INF/classes/osuser.xml' specifies a datasource named 'java:comp/env/jdbc/JiraDS', the datasource specified in server.xml or confluence.xml must be 'jdbc/JiraDS'. ## The Confluence login page loads with 'HTTP Status 404' and the output log shows a 'java.lang.ClassNotFoundException' error for the driver, eg 'com.mysql.jdbc.Driver' The database driver library is missing from your Confluence/application server installation. In your Confluence Standalone or Apache Tomcat installation, download the database jar to the common/lib directory.

Document generated by Confluence on Nov 05, 2009 23:34