KB-1690 Users unable to login using Appian authentication after upgrade

Jordan Horwat — Tue, 04 Sep 2018 21:38:54 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 9/4/2018 9:38:54 PM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

The db_PE**.log file located in <APPIAN_HOME>\logs should have entries of the following type, indicating the engine migration was successful:

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

However these entries are missing in this log file, which indicates that the <APPIAN_HOME>\server\personalization\gw1\ag**.kdb file was not migrated properly during the upgrade.

Cause

Personalization engine KDB file was not properly copied over during the migration.

Action

Perform the upgrade again and ensure that all KDB files are properly copied during the migration. The Copy Your Engine Data section of the Upgrade Guide explains the proper way to migrate engine data during an Appian upgrade.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Tejas Kargutkar — Tue, 04 Sep 2018 10:16:09 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 9/4/2018 10:16:09 AM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

The db_PE**.log file located in <APPIAN_HOME>\logs should have entries of the following type which indicates the engine migration was successful. However the entries of the following type are missing in this log file which indicates the <APPIAN_HOME>\server\personalization\gw1\ag**.kdb file was not migrated over.

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Cause

Personalization engine kdb was not properly copied over during the migration.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Tejas Kargutkar — Fri, 24 Aug 2018 11:57:48 GMT

Revision 6 posted to Appian Knowledge Base by Tejas Kargutkar on 8/24/2018 11:57:48 AM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Cause

Personalization engine kdb was not properly copied over during the migration.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Tom Ryan — Thu, 23 Aug 2018 22:49:16 GMT

Revision 5 posted to Appian Knowledge Base by Tom Ryan on 8/23/2018 10:49:16 PM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

Cause

Some engine data was not properly copied over during the migration.

This can be confirmed by checking the db_**.log file (located in <APPIAN_HOME>\logs\) of the respective engine. The absence of log entries of the following type indicates that the engine was not migrated correctly:

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Parmida Borhani — Wed, 22 Aug 2018 21:56:42 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 8/22/2018 9:56:42 PM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

Cause

Some engine data was not properly copied over during the migration.

This can be confirmed by checking the db_**.log file (located in <APPIAN_HOME>\logs\) of the respective engine. The absence log entries of the following type indicates that the engine was not migrated:

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Tejas Kargutkar — Wed, 22 Aug 2018 19:50:46 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 8/22/2018 7:50:46 PM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

Cause

Some engines were not copied over during the migration.

This can be confirmed by checking the <APPIAN_HOME>\logs\db_** of the respective engine. Not having log entries of the following type indicates that the engine was not migrated:

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Action

Redo the migration and ensure the all kdbs are copied during the migration as per this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Jordan Horwat — Wed, 22 Aug 2018 17:20:34 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 8/22/2018 5:20:34 PM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

Cause

Some engine data were not properly copied over during the migration.

This can be confirmed by checking the <APPIAN_HOME>\logs\db_**.log file of the respective engine. The absence log entries of the following type indicates that the engine was not migrated:

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Users unable to login via Appian authentication after upgrade

Jordan Horwat — Wed, 22 Aug 2018 17:17:35 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 8/22/2018 5:17:35 PM

Symptoms

After an Appian upgrade, users are unable to log into the environment when using basic Appian authentication.

Cause

Some engine data were not properly copied over during the migration.

This can be confirmed by checking the <APPIAN_HOME>\logs\db_**.log file of the respective engine. The absence log entries of the following type indicates that the engine was not migrated:

[PE1] {ag3.kdb 0} (Base) INFO .migrate "<PERCENTAGE OF MIGRATION>% Migrating from version: <APPIAN VERSION>"

Action

Redo the migration and ensure that all KDB files are properly copied during the migration as explained in this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure