KB-2164 Application server cannot start with "Failed to create DesignObjectSchema" errors in high availability or distributed environments

Parmida Borhani — Fri, 13 Nov 2020 05:51:09 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 11/13/2020 5:51:09 AM

Symptoms

In a highly-available or distributed Appian environment, the application server fails to start and the following error error is logged in the application server logs:

ERROR com.appiancorp.ads.designobjects.schema.DesignObjectSchemaManager - APNX-1-4408-001 - Failed to create DesignObjectSchema.
ERROR com.appiancorp.applicationpatch.PatchSchemaManager - APNX-1-4506-001 - Failed to connect to data server. The ability to store and retrieve application patches will not be available until the connection is reestablished. Check the status of the data server.

Although the errors indicate an issue with the data server, the data server itself may start and run, but the application server on all nodes in the high availability set-up fail to start successfully as a result.

Cause

This error can appear when the data-server-sec.properties file is inconsistent between all nodes where the application server or data server is installed. See the following documentation for more details.

Action

Follow the documented procedures to set the security token and ensure that the dataserver.password property is consistent across all distributed nodes.
Restart the data server according to the steps listed in the documentation and confirm that the process is running.
Start the application server.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: November 2020

Tags: high availability, installation, application server, ads, distributed, data-server

DRAFT SP-4122 Application server cannot start with "Failed to create DesignObjectSchema" errors in high availability or distributed environments

Jason Ly — Wed, 11 Nov 2020 01:49:49 GMT

Revision 6 posted to Appian Knowledge Base by Jason Ly on 11/11/2020 1:49:49 AM

Symptoms

In a highly-available or distributed Appian environment, the application server fails to start and the following error error is logged in the application server logs:

ERROR com.appiancorp.ads.designobjects.schema.DesignObjectSchemaManager - APNX-1-4408-001 - Failed to create DesignObjectSchema.
ERROR com.appiancorp.applicationpatch.PatchSchemaManager - APNX-1-4506-001 - Failed to connect to data server. The ability to store and retrieve application patches will not be available until the connection is reestablished. Check the status of the data server.

Cause

Action

Follow the documented procedures to set the security token and ensure that the dataserver.password property is consistent across all distributed nodes.
Restart the data server according to the steps listed in the documentation and confirm that the process is running.
Start the application server.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: September 2020

Tags: high availability, installation, application server, distributed, data-server

DRAFT SP-4122 Application server cannot start with "Failed to create DesignObjectSchema" errors in high availability or distributed environments

April Schuppel — Mon, 26 Oct 2020 12:53:42 GMT

Revision 5 posted to Appian Knowledge Base by April Schuppel on 10/26/2020 12:53:42 PM

Symptoms

In a highly-available or distributed Appian environment, the application server fails to start and the following error error is logged in the application server logs:

ERROR com.appiancorp.ads.designobjects.schema.DesignObjectSchemaManager - APNX-1-4408-001 - Failed to create DesignObjectSchema.
ERROR com.appiancorp.applicationpatch.PatchSchemaManager - APNX-1-4506-001 - Failed to connect to data server. The ability to store and retrieve application patches will not be available until the connection is reestablished. Check the status of the data server.

Cause

Action

Follow the documented procedures to set the security token and ensure that the dataserver.password property is consistent across all distributed nodes.
Restart the data server and confirm a successful connection using the <> log. A successful output can be seen below:
Start the application server.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: September 2020

Tags: high availability, installation, application server, distributed, data-server

DRAFT SP-4122 Application server cannot start with "Failed to create DesignObjectSchema" errors in high availability or distributed environments

Parmida Borhani — Wed, 30 Sep 2020 00:52:58 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 9/30/2020 12:52:58 AM

Symptoms

In a highly-available or distributed Appian environment, the application server fails to start and the following error error is logged in the application server logs:

ERROR com.appiancorp.ads.designobjects.schema.DesignObjectSchemaManager - APNX-1-4408-001 - Failed to create DesignObjectSchema.
ERROR com.appiancorp.applicationpatch.PatchSchemaManager - APNX-1-4506-001 - Failed to connect to data server. The ability to store and retrieve application patches will not be available until the connection is reestablished. Check the status of the data server.

Cause

Action

Follow the documented procedures to set the security token and ensure that the dataserver.password property is consistent across all distributed nodes.
Restart the data server and confirm a successful connection using the <> log. A successful output can be seen below:
Start the application server.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: September 2020

Tags: high availability, installation, application server, distributed, data-server

DRAFT SP-4122 Application server cannot start with "Failed to create DesignObjectSchema" errors in High Availability environments

Jason Ly — Tue, 29 Sep 2020 04:47:31 GMT

Revision 3 posted to Appian Knowledge Base by Jason Ly on 9/29/2020 4:47:31 AM

Symptoms

"Failed to create DesignObjectSchema" errors appear in application server logs. Although the data server may start and run, the application server on all separate nodes in the high availability set up will fail to start successfully.

Cause

This error can appear when the dataserver.password property is inconsistent between all nodes.

Action

Ensure that the data servers are able to communicate with one another. This can be done by reviewing the steps in the following documentation:
https://docs.appian.com/suite/help/19.4/Data_Server_Connection_Restrictions.html

Specifically, ensure that the dataserver.password property within the data-server-sec.properties file is consistent across all distributed nodes.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: September 2020

Tags: high availibility, application server, data-server

DRAFT SP-4122 Application server cannot start with "Failed to create DesignObjectSchema" errors in High Availability environments

Jason Ly — Tue, 29 Sep 2020 04:41:32 GMT

Revision 2 posted to Appian Knowledge Base by Jason Ly on 9/29/2020 4:41:32 AM

Symptoms

"Failed to create DesignObjectSchema" errors appear in application server logs. Even though the data server processes may start and run, the application server will fail to start.

Cause

This error can appear when the dataserver.password is inconsistent between all nodes.

Action

Specifically, ensure that the dataserver.password property within the data-server-sec.properties file is consistent across all distributed nodes.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: September 2020

Tags: high availibility, application server, data-server

DRAFT SP-4122 Application server cannot start with "Failed to create DesignObjectSchema" errors in High Availability environments

Jason Ly — Tue, 29 Sep 2020 04:41:08 GMT

Revision 1 posted to Appian Knowledge Base by Jason Ly on 9/29/2020 4:41:08 AM

Symptoms

"Failed to create DesignObjectSchema" errors appear in application server logs. Even though the data server processes may start and run, the application server will fail to start.

Cause

This error can appear when the dataserver.password is inconsistent between all nodes.

Action

Specifically, ensure that the dataserver.password property within the data-server-sec.properties file is consistent across all distributed nodes.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

Affected Versions

This article applies to Appian 19.4 and later.

Last Reviewed: September 2020

Tags: high availibility, application server, data-server