KB-2056 "Error creating bean with name 'localeConfig': User does not have the rights to perform this operation" when starting the application server

Parmida Borhani — Tue, 14 Jan 2020 23:41:42 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/14/2020 11:41:42 PM

Symptoms

The application server is unable to start. The application server log indicates that it is unable to create the Java bean with the name localeConfig:

com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localeConfig' defined in com.appiancorp.common.spring.BootstrapSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.ap2.LocaleConfig]: Factory method 'localeConfig' threw exception; nested exception is java.lang.RuntimeException: PrivilegeException[null=>null]: User does not have the rights to perform this operation

Cause

The portal engine booted from an inconsistent or blank KDB. This can happen after an incorrectly executed upgrade or migration.

Action

Check that any expected symlinks are in place for the engine <APPIAN_HOME>/server/portal/gw1 folder. Ensure that the portal engine is using the appropriate KDB file when booting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: engines, portal-engine, application server, upgrade, infrastructure

DRAFT KB-XXXX "Error creating bean with name 'localeConfig': User does not have the rights to perform this operation" when starting the application server

Tristan Newmann — Fri, 10 Jan 2020 06:04:31 GMT

Revision 4 posted to Appian Knowledge Base by Tristan Newmann on 1/10/2020 6:04:31 AM

Symptoms

The application server is unable to start. The application server log indicates that it is unable to create the Java bean with the name localeConfig:

com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localeConfig' defined in com.appiancorp.common.spring.BootstrapSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.ap2.LocaleConfig]: Factory method 'localeConfig' threw exception; nested exception is java.lang.RuntimeException: PrivilegeException[null=>null]: User does not have the rights to perform this operation

Cause

The portal engine booted from an inconsistent or blank KDB. This can happen after an incorrectly executed upgrade or migration.

Action

Check that any expected symlinks are in place for the engine <APPIAN_HOME>/server/portal/gw1 folder. Ensure that the portal engine is using the appropriate KDB file when booting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: engines, portal-engine, application server, upgrade, infrastructure

DRAFT KB-XXXX "Error creating bean with name 'localeConfig': User does not have the rights to perform this operation" when starting the application server

Tristan Newmann — Fri, 10 Jan 2020 00:22:22 GMT

Revision 3 posted to Appian Knowledge Base by Tristan Newmann on 1/10/2020 12:22:22 AM

Symptoms

The application server is unable to start. The application server log indicates that it is unable to create the Java bean with the name localeConfig:

com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localeConfig' defined in com.appiancorp.common.spring.BootstrapSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.ap2.LocaleConfig]: Factory method 'localeConfig' threw exception; nested exception is java.lang.RuntimeException: PrivilegeException[null=>null]: User does not have the rights to perform this operation

Cause

The portal engine booted from an inconsistent or blank KDB. This can happen after an incorrectly executed upgrade or migration.

Action

Check that any expected symlinks are in place for the engine <APPIAN_HOME>/server/portal/gw1 folder. Ensure that the portal engine is using the appropriate KDB file when booting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: engines, portal-engine, upgrade, infrastructure

DRAFT KB-XXXX "Error creating bean with name 'localeConfig': User does not have the rights to perform this operation" when starting the application server

Parmida Borhani — Fri, 10 Jan 2020 00:11:17 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 1/10/2020 12:11:17 AM

Symptoms

The application server is unable to start. The application server log indicates that it is unable to create the Java bean with the name localeConfig:

com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localeConfig' defined in com.appiancorp.common.spring.BootstrapSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.ap2.LocaleConfig]: Factory method 'localeConfig' threw exception; nested exception is java.lang.RuntimeException: PrivilegeException[null=>null]: User does not have the rights to perform this operation

Cause

The portal engine booted from an inconsistent or blank KDB. This can happen after an incorrectly executed upgrade or migration.

Action

Check that any expected symlinks are in place for the engine gw folder. Ensure that the portal engine is using the appropriate KDB file when booting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: engines, upgrade, infrastructure

"Error creating bean with name 'localeConfig': User does not have the rights to perform this operation" when starting the application server

Tristan Newmann — Thu, 09 Jan 2020 04:51:35 GMT

Revision 1 posted to Appian Knowledge Base by Tristan Newmann on 1/9/2020 4:51:35 AM

Symptoms

The application server is unable to start. The application server log indicates that it is unable to create the java bean with the name localeConfig:

com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localeConfig' defined in com.appiancorp.common.spring.BootstrapSpringConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.ap2.LocaleConfig]: Factory method 'localeConfig' threw exception; nested exception is java.lang.RuntimeException: PrivilegeException[null=>null]: User does not have the rights to perform this operation

Cause

The portal engine booted from an inconsistent or blank kdb. This may happen after an incorrectly executed upgrade or migration.

Action

Check that any expected symlinks are in place for the engine gw folder.
Ensure that the portal engine is using the appropriate kdb file when booting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: engines, upgrade, infrastructure