KB-1496 /design and /admin do not load after an upgrade

Parmida Borhani — Mon, 23 Jul 2018 03:32:52 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:32:52 AM

Symptoms

After an upgrade, navigating to <APPIAN_URL>/suite/design and <APPIAN_URL>/suite/admin shows a brief "Working" indicator and then only shows the background screen, and the following error is seen in the application server log:

INFO [stdout] (ajp-/0.0.0.0:8009-13) com.appiancorp.process.expression.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error : Rule 'uisubmittableform' has X parameters, but instead passed Y parameters. (APNX-1-4198-000)

where X and Y may be any number.

Cause

This occurs as a result of an improper migration. Appian is attempting to call the rules as defined in the upgraded version, however, its references to these rules are still from the pre-upgrade version.

Action

Redo the migration, making sure to exactly follow the steps in the upgrade guide. In particular, make sure the engines are fully shut down before migrating them, and that all of the components being migrated are from the same timestamp.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2018

Tags: installation, upgrade, infrastructure

KB-1496 /design and /admin do not load after an upgrade

Nick Vigilante — Wed, 14 Feb 2018 17:52:51 GMT

Revision 4 posted to Appian Knowledge Base by Nick Vigilante on 2/14/2018 5:52:51 PM

Symptoms

INFO [stdout] (ajp-/0.0.0.0:8009-13) com.appiancorp.process.expression.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error : Rule 'uisubmittableform' has X parameters, but instead passed Y parameters. (APNX-1-4198-000)

where X and Y may be any number.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2018

Tags: upgrade

DRAFT KB-XXXX /design and /admin do not load after an upgrade

Parmida Borhani — Tue, 13 Feb 2018 22:10:01 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 2/13/2018 10:10:01 PM

Symptoms

INFO [stdout] (ajp-/0.0.0.0:8009-13) com.appiancorp.process.expression.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error : Rule 'uisubmittableform' has X parameters, but instead passed Y parameters. (APNX-1-4198-000)

where X and Y may be any number.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2018

Tags: upgrade

DRAFT KB-XXXX /design and /admin do not load after an upgrade

Parmida Borhani — Tue, 13 Feb 2018 22:07:11 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 2/13/2018 10:07:11 PM

Symptoms

INFO [stdout] (ajp-/0.0.0.0:8009-13) com.appiancorp.process.expression.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error : Rule 'uisubmittableform' has X parameters, but instead passed Y parameters. (APNX-1-4198-000)

where X and Y may be any number.

Cause

Action

Redo the migration, making sure to exactly follow the steps in the upgrade guide.

In particular, make sure the engines are fully shut down before migrating them, and that all of the components being migrated are from the same timestamp.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2018

Tags: upgrade

DRAFT KB-XXXX /design and /admin do not load after an upgrade

Cali Nelson — Tue, 13 Feb 2018 14:11:06 GMT

Revision 1 posted to Appian Knowledge Base by Cali Nelson on 2/13/2018 2:11:06 PM

Symptoms

After an upgrade, navigating to /design and /admin shows a brief "Working" box and then only shows the background screen, and the following errors are seen in the log:

INFO [stdout] (ajp-/0.0.0.0:8009-13) com.appiancorp.process.expression.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error : Rule 'uisubmittableform' has X parameters, but instead passed Y parameters. (APNX-1-4198-000)

where X and Y may be any number.

Cause

This occurs as a result of an improper migration.

The cause for this is that Appian is attempting to call the rules as defined in the upgraded version, however, its references to these rules are still from the pre-upgrade version.

Action

Redo the migration, making sure to exactly follow the steps in the upgrade guide.

In particular, make sure the engines are fully shut down before you migrate them, and that all of the components being migrated are from the same timestamp.

Affected Versions

This article applies to all versions of Appian.

Tags: appian objects, upgrade