Unable to Connect to Database Due to Database Authentication
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
Symptoms
Symptoms include:
The JIRA context fails to initialize.
The browser displays
HTTP Status 404 - The requested resource is not available.
Application logs contain the following error:
1
2
3
4
5
2007-09-25 10:51:39,623 Thread-1 ERROR [atlassian.jira.service.DefaultServiceManager] Could not configure services:
org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Cannot create PoolableConnectionFactory (Login failed for user 'jirauser'.))
at org.ofbiz.core.entity.jdbc.SQLProcessor.getConnection(SQLProcessor.java:239)
at org.ofbiz.core.entity.jdbc.SQLProcessor.prepareStatement(SQLProcessor.java:318)
at org.ofbiz.core.entity.GenericDAO.selectListIteratorByCondition(GenericDAO.java:1024)
Cause
The credentials used to login to the DBMS are invalid, don't exist or are missing sufficient permissions to connect.
Resolution
Verify the username and password used in the JDBC driver definition.
Ensure that the DBMS user exists and the permissions granted are sufficient.
ℹ️ If you're trying to connect to a MS SQL database that is running on a port that is not the default (non-standard), please take a look through this MSDN blog on tips for making application connectivity work.
Was this helpful?