KB-1140 Errors upgrading Appian to 16.2 using SQL Server as the Appian datasource

Parmida Borhani — Mon, 30 Jul 2018 03:40:59 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:40:59 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Upgrading to 16.2 using Microsoft SQL Server as the Appian datasource fails with the following error in the application server log:

Error creating bean with name 'keyStoreConfig' defined in class com.appiancorp.common.crypto.CryptoSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.common.crypto.KeyStoreConfig]: Factory method 'keyStoreConfig' threw exception; nested exception is org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.appiancorp.common.config.persistence.Config.isDefault

Cause

This issue has been addressed via AN-69760 in the following hotfixes/versions:

Appian 16.2 Hotfix Package A
Appian 16.3

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian

Workaround

To workaround this issue, follow the steps below:

Login to the SQL Server and access the Appian datasource.
Execute the following query:
UPDATE cfg SET is_default=0;
Restart the application server.

Affected Versions

This article applies to Appian 16.2 using Microsoft SQL Server 2008 or 2012 as the Appian datasource.

Last Reviewed: February 2017

Tags: sql server, known issues, database, installation, fixed issues, upgrade, infrastructure

KB-1140 Errors upgrading Appian to 16.2 using SQL Server as the Appian datasource

Nick Vigilante — Thu, 13 Jul 2017 16:25:36 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 7/13/2017 4:25:36 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Upgrading to 16.2 using Microsoft SQL Server as the Appian datasource fails with the following error in the application server log:

Error creating bean with name 'keyStoreConfig' defined in class com.appiancorp.common.crypto.CryptoSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.common.crypto.KeyStoreConfig]: Factory method 'keyStoreConfig' threw exception; nested exception is org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.appiancorp.common.config.persistence.Config.isDefault

Cause

This issue has been addressed via AN-69760 in the following hotfixes/versions:

Appian 16.2 Hotfix Package A
Appian 16.3

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian

Workaround

To workaround this issue, follow the steps below:

Login to the SQL Server and access the Appian datasource.
Execute the following query:
UPDATE cfg SET is_default=0;
Restart the application server.

Affected Versions

This article applies to Appian 16.2 using Microsoft SQL Server 2008 or 2012 as the Appian datasource.

Last Reviewed: February 2017

Tags: sql server, known issues, database, fixed issues, upgrade

KB-1140 Errors upgrading Appian to 16.2 using SQL Server as the Appian datasource

Victoria Ebel — Fri, 24 Feb 2017 15:50:57 GMT

Revision 2 posted to Appian Knowledge Base by Victoria Ebel on 2/24/2017 3:50:57 PM

Symptoms

Upgrading to 16.2 using Microsoft SQL Server as the Appian datasource fails with the following error in the application server log:

Error creating bean with name 'keyStoreConfig' defined in class com.appiancorp.common.crypto.CryptoSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.common.crypto.KeyStoreConfig]: Factory method 'keyStoreConfig' threw exception; nested exception is org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.appiancorp.common.config.persistence.Config.isDefault

Cause

This issue has been addressed via AN-69760 in the following hotfixes/versions:

Appian 16.2 Hotfix Package A
Appian 16.3

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian

Workaround

To workaround this issue, follow the steps below:

Login to the SQL Server and access the Appian datasource.
Execute the following query:
UPDATE cfg SET is_default=0;
Restart the application server.

Affected Versions

This article applies to Appian 16.2 using Microsoft SQL Server 2008 or 2012 as the Appian datasource.

Last Reviewed: February 2017

Tags: sql server, known issues, database, fixed issues, upgrade

KB-1140 Errors upgrading Appian to 16.2 using SQL Server as the Appian datasource

Nick Vigilante — Fri, 24 Feb 2017 14:57:44 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 2:57:44 PM

Symptoms

Upgrading to 16.2 using Microsoft SQL Server as the Appian datasource fails with the following error in the application server log:

Error creating bean with name 'keyStoreConfig' defined in class com.appiancorp.common.crypto.CryptoSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.common.crypto.KeyStoreConfig]: Factory method 'keyStoreConfig' threw exception; nested exception is org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.appiancorp.common.config.persistence.Config.isDefault

Cause

This issue has been addressed via AN-69760 in the following hotfixes/versions:

Appian 16.2 Hotfix Package A
Appian 16.3

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

To workaround this issue, follow the steps below:

Login to the SQL Server and access the Appian datasource.
Execute the following query:
UPDATE cfg SET is_default=0;
Restart the application server.

Affected Versions

This article applies to Appian 16.2 using Microsoft SQL Server 2008 or 2012 as the Appian datasource.

Last Reviewed: February 2017

Tags: sql server, known issues, database, fixed issues, upgrade