https://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasourceen-USTelligent Community 12https://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasourceWed, 03 Oct 2018 04:22:41 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33a630aa-25c0-4057-a028-09a4d3cc29bbParmida Borhanihttps://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 10/3/2018 4:22:41 AM<br /> <h2>Symptoms</h2> <p>Tomcat fails to deploy Appian with the following error in <code>&lt;APPIAN_HOME&gt;/logs/tomcat-stdOut.log</code>:</p> <pre>WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference<br /> java.lang.IllegalArgumentException: Illegal base64 character 3a</pre> <h2>Cause</h2> <p>The un-encoded database password contains special characters which causes an issue with the encoding&nbsp;and decoding done by Tomcat. The Appian Team has observed this issue when the database password contained the &quot;:&quot; character.</p> <h2>Action</h2> <p>Ensure that special characters are not included in the un-encoded database password.</p> <h2>Affected Versions</h2> <p>This article applies to Appian 18.3 and later.</p> <p>Last Reviewed: September 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Tomcat, database, application server, infrastructure</div> https://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource/revision/4Tue, 25 Sep 2018 09:22:54 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33a630aa-25c0-4057-a028-09a4d3cc29bbRebecca Jonashttps://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource#commentsRevision 4 posted to Appian Knowledge Base by Rebecca Jonas on 9/25/2018 9:22:54 AM<br /> <h2>Symptoms</h2> <p>Tomcat fails to deploy Appian with the following error in <code>&lt;APPIAN_HOME&gt;/logs/tomcat-stdOut.log</code>:</p> <pre>WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference<br /> java.lang.IllegalArgumentException: Illegal base64 character 3a</pre> <h2>Cause</h2> <p>The un-encoded database password contains special characters which causes an issue with the encoding&nbsp;and decoding done by Tomcat. The Appian Team has observed this issue when the database password contained the &quot;:&quot; character.</p> <h2>Action</h2> <p>Ensure that special characters are not included in the un-encoded database password.</p> <h2>Affected Versions</h2> <p>This article applies to Appian 18.3 and later.</p> <p>Last Reviewed: September 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Tomcat, database, application server, infrastructure</div> https://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource/revision/3Mon, 24 Sep 2018 17:31:15 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33a630aa-25c0-4057-a028-09a4d3cc29bbRebecca Jonashttps://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource#commentsRevision 3 posted to Appian Knowledge Base by Rebecca Jonas on 9/24/2018 5:31:15 PM<br /> <h2>Symptoms</h2> <p>Tomcat fails to deploy Appian with the following error in <code>&lt;APPIAN_HOME&gt;/logs/tomcat-stdOut.log</code>:</p> <pre>WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference<br /> java.lang.IllegalArgumentException: Illegal base64 character 3a</pre> <h2>Cause</h2> <p>The un-encoded database password contains special characters which causes an issue with the encoding&nbsp;and decoding done by Tomcat. The Appian Team has observed this issue when the database password contained the &quot;:&quot; character.</p> <h2>Action</h2> <p>Ensure that special characters are not included in the un-encoded database password.</p> <h2>Affected Versions</h2> <p>This article applies to Appian 18.3 and later.</p> <p>Last Reviewed: September 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Tomcat, database, application server</div> https://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource/revision/2Mon, 24 Sep 2018 17:30:21 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33a630aa-25c0-4057-a028-09a4d3cc29bbRebecca Jonashttps://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource#commentsRevision 2 posted to Appian Knowledge Base by Rebecca Jonas on 9/24/2018 5:30:21 PM<br /> <h2>Symptoms</h2> <p>Tomcat fails to deploy Appian with the following error in <code>&lt;APPIAN_HOME&gt;/logs/tomcat-stdOut.log</code>:</p> <pre>WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference<br /> java.lang.IllegalArgumentException: Illegal base64 character 3a</pre> <h2>Cause</h2> <p>The un-encoded database password contains special characters which causes an issue with the encoding&nbsp;and decoding done by Tomcat. The Appian Team has observed this issue when the database password contained the &quot;:&quot; character.</p> <h2>Action</h2> <p>Ensure that special characters are not included in the un-encoded database password.</p> <h2>Affected Versions</h2> <p>This article applies to Appian 18.3 and later.</p> <p>Last Reviewed: September 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Tomcat, database, application server</div> https://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource/revision/1Fri, 21 Sep 2018 15:23:41 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33a630aa-25c0-4057-a028-09a4d3cc29bbRebecca Jonashttps://community.appian.com/support/w/kb/1145/kb-1734-tomcat-fails-to-deploy-appian-with-illegalargumentexception-when-connecting-to-the-primary-datasource#commentsRevision 1 posted to Appian Knowledge Base by Rebecca Jonas on 9/21/2018 3:23:41 PM<br /> <h2>Symptoms</h2> <p>Tomcat fails with the following error in <code>&lt;APPIAN_HOME&gt;/logs/tomcat-stdOut.log</code>:</p> <pre>WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference<br /> java.lang.IllegalArgumentException: Illegal base64 character 3a</pre> <h2>Cause</h2> <p>The database password contains special characters. Special characters are not compatible with the encoding done using the configure script and decoding done by Tomcat upon starting the application server. When the encoded password is read from the&nbsp;<strong>suite.xml</strong> file, Tomcat will be unable to decode the encoded special characters and will fail to start.</p> <h2>Action</h2> <p>Ensure that you do not include special characters in your database password.</p> <h2>Affected Versions</h2> <p>This article applies to Appian 18.3 and later.</p> <p>Last Reviewed: September 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Tomcat, database, application server</div>