KB-1485 "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_*.log

Nick Vigilante — Wed, 31 Jan 2018 19:14:50 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 1/31/2018 7:14:50 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_*.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Both of the above symptoms must be present before proceeding to the following sections. If the migration.kr: file not found error is seen, please refer to the next section. If not, refer to the steps in KB-1211 to see if this applies to the observed issue.

Cause

The migration.kr present in <APPIAN_HOME>/server/*engine*/migration directory or the migration folder present in <APPIAN_HOME>/server/*engine* directory is missing. This may be due to deleting it accidentally or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

KB-1485 "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_*.log

Nick Vigilante — Wed, 31 Jan 2018 14:14:50 GMT

Revision 15 posted to Appian Knowledge Base by Nick Vigilante on 1/31/2018 2:14:50 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_*.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

DRAFT KB-XXXX "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_**.log

Tejas Kargutkar — Wed, 31 Jan 2018 12:58:40 GMT

Revision 14 posted to Appian Knowledge Base by Tejas Kargutkar on 1/31/2018 12:58:40 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration.kr present in <APPIAN_HOME>/server/*engine*/migration directory or the migration folder present in <APPIAN_HOME>/server/*engine* directory is missing. This may be due to accidentally deleting it or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

DRAFT KB-XXXX "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_**.log

Parmida Borhani — Tue, 30 Jan 2018 20:16:01 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2018 8:16:01 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing. This may be due to accidentally deleting it or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

DRAFT KB-XXXX "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_**.log

Tejas Kargutkar — Tue, 30 Jan 2018 18:14:06 GMT

Revision 12 posted to Appian Knowledge Base by Tejas Kargutkar on 1/30/2018 6:14:06 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Both of the above symptoms must be present before proceeding to the following sections. If the migration.kr: file not found error is seen, please refer to the next section. If not, you can refer to the steps in KB-1211 to see if this applies to the issue you observe.

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing. This may be due to accidentally deleting it or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

DRAFT KB-XXXX "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_**.log

Parmida Borhani — Mon, 29 Jan 2018 17:57:59 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 5:57:59 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Both of the above symptoms must be present before proceeding to the following sections. If the migration.kr: file not found error is not seen, follow the steps in KB-1211.

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing. This may be due to accidentally deleting it or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

DRAFT KB-XXXX "Inconsistent DBID on GW1" error thrown in checkengine script and engines fail to boot up with "migration.kr: file not found" error in db_**.log

Parmida Borhani — Mon, 29 Jan 2018 17:56:13 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 5:56:13 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

YYYY-MM-DD HH:MM:SS [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Both of the above symptoms must be present before proceeding to the following sections.

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing. This may be due to accidentally deleting it or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier.

Last Reviewed: January 2018

Tags: engines, installation, upgrade

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Mon, 29 Jan 2018 16:44:58 GMT

Revision 9 posted to Appian Knowledge Base by Tejas Kargutkar on 1/29/2018 4:44:58 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

2016-10-24 21:05:48 [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Only if you observe the above two symptoms, proceed to the following section to understand the "Cause" and the "Action".

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier

Last Reviewed: January 2018

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Mon, 29 Jan 2018 16:40:32 GMT

Revision 8 posted to Appian Knowledge Base by Tejas Kargutkar on 1/29/2018 4:40:32 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

2016-10-24 21:05:48 [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Only if you observe the above two symptoms, proceed to the following section to understand the "Cause" and the "Action".

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Mon, 29 Jan 2018 16:38:16 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 1/29/2018 4:38:16 PM

Symptoms

After attempting to start the engines via the start-suite script, the checkengine script displays an error like this:

On examining the db_**.log for the relevant engine, the following error is seen:

2016-10-24 21:05:48 [PO1] {ap39.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Only if you observe the above two symptoms, proceed to the following section to understand the "Cause" and the "Action".

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to Appian 17.2 and earlier

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Fri, 26 Jan 2018 15:30:56 GMT

Revision 6 posted to Appian Knowledge Base by Tejas Kargutkar on 1/26/2018 3:30:56 PM

Symptoms

User tries to start engines via the start-suite script.

Checkengine script displays an error of the following type:

On examining the db_** log for the relevant engine, you see an error of the following type:

2016-10-24 21:05:48 [CH1] {channels43.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to all versions of Appian older than v.17.3.

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Thu, 25 Jan 2018 20:29:00 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 1/25/2018 8:29:00 PM

Symptoms

User tries to start engines via the start-suite script.

Checkengine script displays an error of the following type:

On examining the db_** log for the relevant engine, you see an error of the following type:

2016-10-24 21:05:48 [CH1] {channels43.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <Appian_home>\server\*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Thu, 25 Jan 2018 16:09:14 GMT

Revision 5 posted to Appian Knowledge Base by Tejas Kargutkar on 1/25/2018 4:09:14 PM

Symptoms

User tries to start engines via the start-suite script.

Checkengine script displays an error of the following type:

On examining the db_** log for the relevant engine, you see an error of the following type:

2016-10-24 21:05:48 [CH1] {channels43.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <APPIAN_HOME>/server/*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to all versions of Appian older than v.17.3.

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Thu, 25 Jan 2018 16:05:08 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 1/25/2018 4:05:08 PM

Symptoms

User tries to start engines via the start-suite script.

Checkengine script displays an error of the following type:

On examining the db_** log for the relevant engine, you see an error of the following type:

2016-10-24 21:05:48 [CH1] {channels43.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <Appian_home>\server\*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Affected Versions

This article applies to all versions of Appian older than v.17.3.

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Thu, 25 Jan 2018 15:34:07 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 1/25/2018 3:34:07 PM

Symptoms

User tries to start engines via the start-suite script.

Checkengine script displays an error of the following type:

On examining the db_** log for the relevant engine, you see an error of the following type:

2016-10-24 21:05:48 [CH1] {channels43.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <Appian_home>\server\*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Tags: engines

DRAFT KB-XXXX Engines fail to boot up with "migration.kr: file not found" error

Tejas Kargutkar — Thu, 25 Jan 2018 15:33:42 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 1/25/2018 3:33:42 PM

Symptoms

User tries to start engines via the start-suite script.

Checkengine script displays an error of the following type:

On examining the db_** log for the relevant engine, you see an error of the following type:

2016-10-24 21:05:48 [CH1] {channels43.kdb ,6713} () FATAL .a.db "migration.kr: file not found"

Cause

The migration directory present in <Appian_home>\server\*engine* directory is missing due to accidentally deleting or moving it to a different location.

Action

Re-install Appian and test the install/upgrade again.

Tags: engines