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:
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
The portal engine booted from an inconsistent or blank KDB. This can happen after an incorrectly executed upgrade or migration.
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.
<APPIAN_HOME>/server/portal/gw1
This article applies to all versions of Appian.
Last Reviewed: January 2020