KB-1274 "ORA-01017: invalid username/password; logon denied" error thrown during application server startup

Parmida Borhani — Fri, 18 Jan 2019 00:54:35 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/18/2019 12:54:35 AM

Symptoms

18.3 and Later

The application server fails to startup with the following message in the tomcat-stdOut.log file located in the <APPIAN_HOME>/logs directory:

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference java.sql.SQLException: Cannot create PoolableConnectionFactory (ORA-01017: invalid username/password; logon denied)

18.2 and Earlier

The application server fails to startup with the following error in the server.log located in the <JBOSS_HOME>/standalone/logs directory:

WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 55) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:525)
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:434)
...
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

Cause

There are two possible causes for this issue:

The username and/or password the application server is using to connect to the database is not correct.
A special character is included in the password, which can cause issues when the application server attempts to connect to Oracle databases.

Action

Check that you can login directly to the database using the username and plain text password. If not, update the username and password to the correct credentials.
Ensure that the password the application server is using to connect to the Oracle database does not contain a special character and that the credentials are correct. For Appian 18.3 and later, the credentials can be verified in the suite.xml file located in the <APPIAN_HOME>/tomcat/apache-tomcat/conf/Catalina/localhost/ directory. For Appian 18.2 and earlier, the credentials can be verified in the standalone.xml file location in the <JBOSS_HOME>/standalone/configuration directory.
If special characters cannot be removed from the password, ensure to escape them. For example, use "&amp" for & and "&dollar" for $.

Affected Versions

This article applies to all versions of Appian using Oracle as a database.

Last Reviewed: January 2019

Tags: database, installation, application server, infrastructure, oracle

KB-1274 "ORA-01017: invalid username/password; logon denied" error thrown during application server startup

Parmida Borhani — Fri, 18 Jan 2019 00:54:03 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 1/18/2019 12:54:03 AM

Symptoms

18.3 and Later

The application server fails to startup with the following message in the tomcat-stdOut.log file located in the <APPIAN_HOME>/logs directory:

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference java.sql.SQLException: Cannot create PoolableConnectionFactory (ORA-01017: invalid username/password; logon denied)

18.2 and Earlier

The application server fails to startup with the following error in the server.log located in the <JBOSS_HOME>/standalone/logs directory:

WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 55) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:525)
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:434)
...
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

Cause

There are two possible causes for this issue:

The username and/or password the application server is using to connect to the database is not correct.
A special character is included in the password, which can cause issues when the application server attempts to connect to Oracle databases.

Action

Check that you can login directly to the database using the username and plain text password. If not, update the username and password to the correct credentials.
Ensure that the password the application server is using to connect to the Oracle database does not contain a special character and that the credentials are correct. For Appian 18.3 and later, the credentials can be verified in the suite.xml file located in the <APPIAN_HOME>/tomcat/apache-tomcat/conf/Catalina/localhost/ directory. For Appian 18.2 and earlier, the credentials can be verified in the standalone.xml file location in the <JBOSS_HOME>/standalone/configuration directory.
If special characters cannot be removed from the password, ensure to escape them. For example, use "&amp" for & and "&dollar" for $.

Affected Versions

This article applies to all versions of Appian using Oracle as a database.

Last Reviewed: January 2019

Tags: database, installation, application server, infrastructure, oracle

KB-1274 "ORA-01017: invalid username/password; logon denied" error thrown during application server startup

Jordan Horwat — Mon, 23 Jul 2018 17:44:01 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 5:44:01 PM

Symptoms

During the application server startup, the following is printed in the console and the application server log:

WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 55) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:525)
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:434)
...
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

Cause

There are two possible causes for this issue:

The username and/or password the application server is using to connect to the database are not correct.
The “$” character is included in the password, which has been known to cause issues when JBOSS attempts to connect to Oracle databases.

Action

Check that you can login directly to the database using the username and plaintext password. If not, update the username and password to the correct credentials.
Ensure that the password JBOSS is using to connect to the Oracle database does not contain the “$” character.

Affected Versions

This article applies to all versions of Appian using Oracle as a database.

Last Reviewed: March 2017

Tags: database, installation, application server, infrastructure

KB-1274 "ORA-01017: invalid username/password; logon denied" error thrown during application server startup

Nick Vigilante — Tue, 07 Mar 2017 15:41:19 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 3:41:19 PM

Symptoms

During the application server startup, the following is printed in the console and the application server log:

WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 55) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:525)
    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:434)
...
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

Cause

There are two possible causes for this issue:

The username and/or password the application server is using to connect to the database are not correct.
The “$” character is included in the password, which has been known to cause issues when JBOSS attempts to connect to Oracle databases.

Action

Check that you can login directly to the database using the username and plaintext password. If not, update the username and password to the correct credentials.
Ensure that the password JBOSS is using to connect to the Oracle database does not contain the “$” character.

Affected Versions

This article applies to all versions of Appian using Oracle as a database.

Last Reviewed: March 2017

Tags: database, application server