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

Parmida Borhani — Mon, 06 May 2019 07:26:40 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 5/6/2019 7:26:40 AM

Symptoms

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.

Cause

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

Action

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

Tags: Tomcat, installation, application server, upgrade

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

Tom Ryan — Mon, 06 May 2019 00:51:15 GMT

Revision 13 posted to Appian Knowledge Base by Tom Ryan on 5/6/2019 12:51:15 AM

Symptoms

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.

Cause

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

Action

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

Tags: Tomcat, installation, application server, upgrade

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

Jordan Horwat — Fri, 03 May 2019 13:40:27 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2019 1:40:27 PM

Symptoms

An issue with a bad key encryption 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.

Cause

This occurs when the wrong encryption for the password section is used within the <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Tags: Tomcat, installation, application server, upgrade

Unexpected exception resolving reference error occurring after upgrading to Appian versions 18.3 and later

Jordan Horwat — Fri, 03 May 2019 13:39:22 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2019 1:39:22 PM

Symptoms

An issue with a bad key encryption 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.

Cause

This occurs when the wrong encryption for the password section is used within the <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Tags: Tomcat, installation, application server, upgrade

Unexpected exception resolving reference error occurring after upgrading to Appian versions 18.3 and later

Ahmad Chakhachiro — Fri, 03 May 2019 00:36:10 GMT

Revision 10 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/3/2019 12:36:10 AM

Symptoms

An issue with a bad key encryption occurs when starting Tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

When starting up Tomcat for the first time the following warning is logged within 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.

Cause

This occurs when using the wrong encryption for the password section within the <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

Use the Configure Script to encode your 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

Tags: Tomcat, installation, application server, upgrade

Unexpected exception resolving reference error occurring after upgrading to Appian versions 18.3 and later

Ahmad Chakhachiro — Fri, 03 May 2019 00:29:44 GMT

Revision 9 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/3/2019 12:29:44 AM

Symptoms

An issue with a bad key encryption occurs when starting Tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

When starting up Tomcat for the first time the following warning is logged within 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.

Cause

This occurs when using the wrong encryption for the password section within the <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

Use the Configure Script to encode your 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

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 04:44:22 GMT

Revision 8 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 4:44:22 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following warning is logged within 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.

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:30:12 GMT

Revision 7 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:30:12 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following warning is logged within 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.

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:29:55 GMT

Revision 6 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:29:55 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following warning is logged within 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.

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.

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:29:11 GMT

Revision 5 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:29:11 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following warning is logged within 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.

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:26:38 GMT

Revision 4 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:26:38 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following warning is logged within 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.

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:24:07 GMT

Revision 3 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:24:07 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following error is logged within the application server log:

Caused by: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
    at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:991)
    at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:847)
    at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(BlowfishCipher.java:319)
    at javax.crypto.Cipher.doFinal(Cipher.java:2164)
    at com.appiancorp.tomcat.encoding.EncodingCryptographer.decodePassword(EncodingCryptographer.java:25)
    at com.appiancorp.tomcat.datasource.EncodedPasswordDataSourceFactory.getObjectInstance(EncodedPasswordDataSourceFactory.java:36)
    at org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:94)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:839

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:23:08 GMT

Revision 2 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:23:08 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following error is logged within the application server log:

Caused by: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
    at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:991)
    at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:847)
    at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(BlowfishCipher.java:319)
    at javax.crypto.Cipher.doFinal(Cipher.java:2164)
    at com.appiancorp.tomcat.encoding.EncodingCryptographer.decodePassword(EncodingCryptographer.java:25)
    at com.appiancorp.tomcat.datasource.EncodedPasswordDataSourceFactory.getObjectInstance(EncodedPasswordDataSourceFactory.java:36)
    at org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:94)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:839

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3

Bad Key Encryption error occurs after upgrading to Appian versions 18.3 onwards

Ahmad Chakhachiro — Thu, 02 May 2019 01:22:40 GMT

Revision 1 posted to Appian Knowledge Base by Ahmad Chakhachiro on 5/2/2019 1:22:40 AM

An issue with a bad key encryption occurs when starting tomcat after performing an upgrade of Appian from a version which required the customer to install their own application server.

Symptoms

When starting up tomcat for the first time the following error is logged within the application server log:

Caused by: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
    at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:991)
    at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:847)
    at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(BlowfishCipher.java:319)
    at javax.crypto.Cipher.doFinal(Cipher.java:2164)
    at com.appiancorp.tomcat.encoding.EncodingCryptographer.decodePassword(EncodingCryptographer.java:25)
    at com.appiancorp.tomcat.datasource.EncodedPasswordDataSourceFactory.getObjectInstance(EncodedPasswordDataSourceFactory.java:36)
    at org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:94)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:839

Cause

This occurs due to using the wrong encryption for the password section within your <APPIAN_HOME>/tomcat/apache-tomcat/tomcatResources.xml file.

Action

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

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, 19.1, 18.4, upgrade, 18.3