KB-1005 FileNotFoundException thrown for accdocs files during application server startup


Missing content in Appian such as profile pictures, cover photos, and navigation content.

The application server starts and the following message appears:

java.io.FileNotFoundException: /path/to/appian/_admin/accdocs1/2/<filename>.xml 


There is an incorrect path specified in custom.properties or partitions.xml. Installations that use remote servers, or those that have more than one application servers will see this issue if the accdocs paths are not correctly configured.


The error indicates that Appian is trying to locate the necessary documents at <path to accdocs>/accdocsX, where X is a number between 1 and 3, but is unable to.

This path is defined in Appian in two different ways:

  • Within <APPIAN_HOME>/runtime_ear/suite.ear/conf/custom.properties

    • The property is conf.suite.BASE_PATH=<path to accdocs>
  • Within <APPIAN_HOME>/server/_conf/partitions.xml

<partition id="1">//<path to accdocs>/accdocs1</partition>
<partition id="2">//<path to accdocs>/accdocs2</partition>
<partition id="3">//<path to accdocs>/accdocs3</partition>

If the application server is running on a separate machine from the engines, verify custom.properties in both servers to see if conf.suite.BASE_PATH is set incorrectly, in which case fix the path in local.properties and run the configure script again on both servers so the custom.properties gets updated.

If conf.suite.BASE_PATH is not used anywhere, then see if you have a partitions.xml that has this old path in the server where Appian runs.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2017