When starting Appian, an error message can be seen in the logs where there seems to be an inconsistency in how a character has been typed in a configuration file and how it is read by the application server.
Examples are given below:
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.AppianPrimaryDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/AppianPrimaryDS'
javax.naming.NameNotFoundException: jdbc.AppianPrimaryDS -- service jboss.naming.context.java."jdbc.AppianPrimaryDS"
However, in both the above examples, jdbc.AppianPrimaryDS does not seem to be explicitly defined as such in any configuration file.
The application server is misreading a character in an expression defined in a configuration file. There are different possible reasons for the issue:
Refer to UTF-8 for more information.
If the character encoding method for the configuration file is not UTF-8, set it to UTF-8.
By default, the application server should be set to UTF-8. If this isn't the case, set it to UTF-8. In order to do so, the following step configuration needs to be enabled depending on the application server used:
This article applies to all versions of Appian.
Last Reviewed: July 2017
© 2020 Appian. All rights reserved.