https://community.appian.com/support/w/kb/245/kb-1019-domain-error-during-appian-engine-startupen-USTelligent Community 12https://community.appian.com/support/w/kb/245/kb-1019-domain-error-during-appian-engine-startupMon, 30 Jul 2018 03:59:30 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d78919d4-53d4-4eba-8539-6e6da7fca258Parmida Borhanihttps://community.appian.com/support/w/kb/245/kb-1019-domain-error-during-appian-engine-startup#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:59:30 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When starting one of the Appian engines and reviewing the corresponding <strong>gw-*.log</strong> file (Unix) or APP window (Windows), users may see <code>Domain Error</code> before the engine attempts to load.</p> <h2 id="cause">Cause</h2> <p>There is a .kdb file in that engine&#39;s KDB directory with a poorly formatted name. For example, a user may copy a .kdb file but not change the name of that copy, leaving <strong>pe10587 - Copy.kdb</strong>. Appian attempts to read the name of the .kdb file and convert &quot;10587 - Copy&quot; to an integer, which fails, resulting in the error.</p> <p>This can occur even if the .kdb file with the poor formatting is not the highest numbered .kdb file in that folder. The issue will still occur even if there is a <strong>pe10588.kdb</strong> file or higher in the same directory as Appian will try to parse all .kdb files in that directory.</p> <h2 id="action">Action</h2> <p>Rename the .kdb file with the unsupported name format or move it out of the directory.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed: October 2015</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, infrastructure</div> https://community.appian.com/support/w/kb/245/kb-1019-domain-error-during-appian-engine-startup/revision/1Fri, 10 Feb 2017 16:30:40 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d78919d4-53d4-4eba-8539-6e6da7fca258Nick Vigilantehttps://community.appian.com/support/w/kb/245/kb-1019-domain-error-during-appian-engine-startup#commentsRevision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/10/2017 4:30:40 PM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When starting one of the Appian engines and reviewing the corresponding <strong>gw-*.log</strong> file (Unix) or APP window (Windows), users may see <code>Domain Error</code> before the engine attempts to load.</p> <h2 id="cause">Cause</h2> <p>There is a .kdb file in that engine&#39;s KDB directory with a poorly formatted name. For example, a user may copy a .kdb file but not change the name of that copy, leaving <strong>pe10587 - Copy.kdb</strong>. Appian attempts to read the name of the .kdb file and convert &quot;10587 - Copy&quot; to an integer, which fails, resulting in the error.</p> <p>This can occur even if the .kdb file with the poor formatting is not the highest numbered .kdb file in that folder. The issue will still occur even if there is a <strong>pe10588.kdb</strong> file or higher in the same directory as Appian will try to parse all .kdb files in that directory.</p> <h2 id="action">Action</h2> <p>Rename the .kdb file with the unsupported name format or move it out of the directory.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed: October 2015</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines</div>