KB-1930 "Unexpected exception resolving reference" error after upgrading to Appian version 18.3 and later


An issue with decoding the data source password occurs when starting Tomcat after an upgrade from Appian 18.2 and earlier to Appian 18.3 and later.

When starting up Tomcat for the first time, the following warning is logged in the application server log:

WARNING [HOSTNAME-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
 javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.


This occurs when there is an issue decoding the password field in the <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.


Use the Configure Script to encode the data source password and use the output to fill in the password property in the <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: May 2019