Hi, I am installing Appian 7.3 on Windows server 2012 i have done all

...com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException.<init>(AppianRuntimeException.java:41) [appian-suiteapi.jar:]
          at com.appiancorp.common.config.FatalConfigurationException.<init>(FatalConfigurationException.java:27) [appian-common.jar:]
          at com.appiancorp.common.crypto.KeyStoreConfig.ensureValidState(KeyStoreConfig.java:95) [appian-common.jar:]
          at com.appiancorp.common.crypto.KeyStoreConfig.finish0(KeyStoreConfig.java:64) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigObjectWithSecurityContext.finish(ConfigObjectWithSecurityContext.java:28) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:66) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:313) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:222) [appian-common.jar:]
          at com.appiancorp.common.config.C...

...onfigObjectRepository.init(ConfigObjectRepository.java:181) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:53) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:47) [appian-common.jar:]
          at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:39) [appian-common.jar:]
          at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
          at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
          at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web...

... -7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_21]
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_21]
          at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_21]
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
          at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
          at org.jboss.threads.JBossThread.run(JBossThread.java:122)

Anyone has faced such issue. How to resolve this? Please suggest.

Are you performing a migration? If not, please ensure that you're using a new data source.

When troubleshooting issues like this one of the best approaches is:

1. Stop the application server
2. Delete the application server log (for JBoss this is <JBOSS_HOME>\\standalone\\log\\*.*
3. Start the application server
4. Wait for the start-up to fail/complete
5. Review the log (server.log) from top to bottom until you find the first relevant error.
6. With that error in mind review the "Caused by" clauses. Usually the last ones will have more information.

In this case case it seems that the original issues you had with your Primary DS introduced an inconsistency between the Appian keystore on disk and the corresponding keystore data in the Primary DS.


For this specific scenario try this approach (APPROACH #1), if it doesn't work use APPROACH #2:

APPROACH #1

0. Stop the application server
1. Delete

<APPIAN_HOME>\\_admin\\shared
<JBOSS_HOME>\\standalone\\log\\*.*

2. Start the application server

APPROACH #2

0. Stop the application server
1. Log-in to the Primary DS
2. Run this query to delete the records from the cfg table

DELETE FROM cfg WHERE prop_key <> '';

3. Delete <APPIAN_HOME>\\_admin\\shared
4. If you had previously placed a passwords.properties under <APPIAN_HOME>\\ear\\suite.ear\\conf to configure passwords such as for Sharepoint or the Email Poller please put it again.
5. Start the application server

Note that the content of <APPIAN_HOME>\\_admin\\shared is encrypted using the information from the cfg table. Therefore, during a migration, it's a must to preserve the original <APPIAN_HOME>\\_admin\\shared and the original Primary DS so that this information can be correctly decrypted during the application server start-up.

In this particular case, you were able to delete the content of the cfg table because in a fresh installation back in 2014 only two rows were present in that table.

That's not the case anymore. Therefore, for those people finding this post, DO NOT USE ANY OF THESE APPROACHES ANY MORE. Please refer to this KB instead forum.appian.com/.../kb-1048.html