KB-1782 Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Mon, 12 Nov 2018 14:39:50 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 2:39:50 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.
1. Additional Context: A SQL dump will contain the SQL statements that should be run in an empty database to regenerate all of the data/tables that existed in the database at the time of the dump. Since the above error "Administration console migration failed." suggests that the migration failed, it would be unexpected to see the SQL statements to update the tables the way a migration would. If the SQL dump does contain these SQL statements, it is likely that the migration has previously been performed.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Thu, 08 Nov 2018 10:42:44 GMT

Revision 18 posted to Appian Knowledge Base by Jordan Horwat on 11/8/2018 10:42:44 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.
1. Additional Context: A SQL dump will contain the SQL statements that should be run in an empty database to regenerate all of the data/tables that existed in the database at the time of the dump. Since the above error "Administration console migration failed." suggests that the migration failed, it would be unexpected to see the SQL statements to update the tables the way a migration would. If the SQL dump does contain these SQL statements, it is likely that the migration has previously been performed.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Wed, 07 Nov 2018 12:56:00 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 11/7/2018 12:56:00 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.
1. Additional Context: A SQL dump will contain the SQL statements that should be run in an empty database to regenerate all of the data/tables that existed in the database at the time of the dump. Since the above error "Administration console migration failed." suggests that the migration failed, it would be unexpected to see the SQL statements to update the tables the way a migration would. If the SQL dump does contain these SQL statements, it is likely that the migration has previously been performed.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Wed, 07 Nov 2018 12:46:19 GMT

Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 11/7/2018 12:46:19 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database. Please reference the following resources for MySQL and SQL Server.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.
1. Additional Context: A SQL dump will contain the SQL statements that should be run in an empty database to regenerate all of the data/tables that existed in the database at the time of the dump. Since the above error "Administration console migration failed." suggests that the migration failed, it would be unexpected to see the SQL statements to update the tables the way a migration would. If the SQL dump does contain these SQL statements, it is likely that the migration has previously been performed.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Wed, 07 Nov 2018 12:45:51 GMT

Revision 15 posted to Appian Knowledge Base by Jordan Horwat on 11/7/2018 12:45:51 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database. Please reference the following resources for MySQL and SQL Server.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.
1. Additional Context: A SQL dump will contain the SQL statements that should be run in an empty database to regenerate all of the data/tables that existed in the database at the time of the dump. Since the above error "Administration console migration failed." suggests that the migration failed, it would be unexpected to see the SQL statements to update the tables the way a migration would. If the SQL dump does contain these SQL statements, it is likely that the migration has previously been performed.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Wed, 07 Nov 2018 12:44:12 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 11/7/2018 12:44:12 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database. Please reference the following resources for MySQL and SQL Server.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.
1. Additional context: A SQL dump will contain the SQL statements that should be run in an empty database to regenerate all of the data/tables that existed in the database at the time of the dump. Since the above error Administration console migration failed. suggests that the migration failed, it would be unexpected to see the SQL statements to update the tables the way a migration would. If the SQL dump does contain these SQL statements, it is likely that the migration has already happened.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 06 Nov 2018 11:00:20 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 11/6/2018 11:00:20 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database. Please reference the following resources for MySQL and SQL Server.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 06 Nov 2018 10:49:01 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 11/6/2018 10:49:01 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT KB-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 06 Nov 2018 10:46:24 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 11/6/2018 10:46:24 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: As this will likely contain PII, please do not upload it to any existing support case. If Appian Support is required to analyze the the SQL dump, it must be examined via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 06 Nov 2018 10:44:00 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 11/6/2018 10:44:00 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: as this will likely contain PII, it may be necessary to examine the contents with the customer via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Thu, 01 Nov 2018 16:44:22 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 11/1/2018 4:44:22 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: as this will likely contain PII, it may be necessary to examine the contents with the customer via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all Appian environments undergoing an upgrade or migration.

Last Reviewed: November 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Thu, 01 Nov 2018 16:40:09 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 11/1/2018 4:40:09 PM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: as this will likely contain PII, it may be necessary to examine the contents with the customer via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all Appian environments undergoing an upgrade or migration.

Last Reviewed: October 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Wed, 31 Oct 2018 10:24:43 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 10/31/2018 10:24:43 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)
...
Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: as this will likely contain PII, it may be necessary to examine the contents with the customer via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to all Appian environments undergoing an upgrade or migration.

Last Reviewed: October 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Application server fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Wed, 31 Oct 2018 10:23:46 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 10/31/2018 10:23:46 AM

Symptoms

The following error is observed in the application server log after an upgrade or migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)
...
Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema. If this is the case, it is likely that the environment is using a database that is not specified in the Appian System Requirements.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: as this will likely contain PII, it may be necessary to examine the contents with the customer via WebEx.
If it is determined that the database cannot support the schema, ensure that the environment is using a database that is specified in the Appian System Requirements.
If it is determined that the migration has previously been performed (e.g. the data that failed to migrate already exists in the database), revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the data migration is only performed one time.

Affected Versions

This article applies to environments that are running on/upgrading to Appian 18.3.

Last Reviewed: October 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Tomcat fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 30 Oct 2018 17:00:40 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 10/30/2018 5:00:40 PM

Symptoms

The following error is observed in the Tomcat log after an upgrade/migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)
...

Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the customer is upgrading to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

DRAFT INT-XXXX Tomcat fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 30 Oct 2018 13:11:04 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 10/30/2018 1:11:04 PM

Symptoms

The following error is observed in the Tomcat log after an upgrade/migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)
...
Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
Examine the SQL dump of the primary database. Note: as this will likely contain PII, it may be necessary to examine the contents with the customer via WebEx.
If it is determined that the database cannot support the schema, ...
If it is determined that the migration has previously been performed, revert the primary database/environment to a backup taken before the upgrade/migration. Perform the upgrade/migration again and ensure that the migration is only performed one time.

Affected Versions

This article applies to environments that are running on/upgrading to Appian 18.3.

Last Reviewed: October 2018

Tags: database, installation, upgrade, infrastructure

DRAFT INT-XXXX Tomcat fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 30 Oct 2018 13:04:46 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 10/30/2018 1:04:46 PM

Symptoms

The following error is observed in the Tomcat log after an upgrade/migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)
...
Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the environment is being upgraded to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

Gather the above information.
If it is determined that the database cannot support the schema, ...
If it is determined that the migration has previously been performed,

DRAFT INT-XXXX Tomcat fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 30 Oct 2018 13:01:32 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 10/30/2018 1:01:32 PM

Symptoms

The following error is observed in the Tomcat log after an upgrade/migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)
...
Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the customer is upgrading to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.

Action

DRAFT INT-XXXX Tomcat fails with "Halting JVM startup: Administration console migration failed." error during an upgrade or migration

Jordan Horwat — Tue, 30 Oct 2018 13:01:08 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 10/30/2018 1:01:08 PM

Symptoms

The following error is observed in the Tomcat log after an upgrade/migration:

FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: Administration console migration failed.
com.appiancorp.suiteapi.common.exceptions.AppianException: Administration console migration failed. (APNX-1-4282-000)

Caused by: java.lang.RuntimeException: Priority '1' is not unique

Cause

The migration of the primary database cannot be completed for one of the following reasons:

The migration has already occurred and is attempting to complete for a second time.
The database software/version cannot support the schema.

In order to determine the exact cause of the issue, the following information is necessary:

The exact version and hotfix the customer is upgrading to and from.
The detailed steps followed to complete the upgrade/migration.
A SQL dump of the primary database.