https://community.appian.com/support/w/kb/489/kb-1278-cannot-migrate-there-is-no-migration-path-error-thrown-in-gw--log-or-app-window-after-engines-fail-to-starten-USTelligent Community 12https://community.appian.com/support/w/kb/489/kb-1278-cannot-migrate-there-is-no-migration-path-error-thrown-in-gw--log-or-app-window-after-engines-fail-to-startThu, 09 Aug 2018 02:14:07 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:7c866cc9-335c-47a6-b848-539ee66b7b1aParmida Borhanihttps://community.appian.com/support/w/kb/489/kb-1278-cannot-migrate-there-is-no-migration-path-error-thrown-in-gw--log-or-app-window-after-engines-fail-to-start#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 8/9/2018 2:14:07 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>Engines fail to boot up. The following error will appear in the <strong>gw-*.log</strong> for Linux and in the app window for Windows:</p> <pre><code>Cannot migrate: There is no migration path </code></pre> <h2 id="cause">Cause</h2> <p>This issue can be caused by one of two things:</p> <ol> <li>You copied engine database files (<strong>*.kdb</strong>) from a newer version of Appian to an older version of Appian. By newer version of Appian, this can include major version (16.3 vs. 16.2) or hotfix (16.2 Hotfix Package B vs 16.2 Hotfix Package A).</li> <li>A hotfix has been recently applied, but this hotfix was applied incorrectly, so the installation now has code mixed from the new hotfix and the previous version/hotfix.</li> </ol> <h2 id="action">Action</h2> <p>If this occurred right after a migration, recopy the engine database files to the same or newer version of Appian.</p> <p>If this occurred right after applying a hotfix, reapply the hotfix.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;March 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, installation, infrastructure</div> https://community.appian.com/support/w/kb/489/kb-1278-cannot-migrate-there-is-no-migration-path-error-thrown-in-gw--log-or-app-window-after-engines-fail-to-start/revision/1Tue, 07 Mar 2017 15:49:43 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:7c866cc9-335c-47a6-b848-539ee66b7b1aNick Vigilantehttps://community.appian.com/support/w/kb/489/kb-1278-cannot-migrate-there-is-no-migration-path-error-thrown-in-gw--log-or-app-window-after-engines-fail-to-start#commentsRevision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 3:49:43 PM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>Engines fail to boot up. The following error will appear in the <strong>gw-*.log</strong> for Linux and in the app window for Windows:</p> <pre><code>Cannot migrate: There is no migration path </code></pre> <h2 id="cause">Cause</h2> <p>This issue can be caused by one of two things:</p> <ol> <li>You copied engine database files (<strong>*.kdb</strong>) from a newer version of Appian to an older version of Appian. By newer version of Appian, this can include major version (16.3 vs. 16.2) or hotfix (16.2 Hotfix Package B vs 16.2 Hotfix Package A).</li> <li>A hotfix has been recently applied, but this hotfix was applied incorrectly, so the installation now has code mixed from the new hotfix and the previous version/hotfix.</li> </ol> <h2 id="action">Action</h2> <p>If this occurred right after a migration, recopy the engine database files to the same or newer version of Appian.</p> <p>If this occurred right after applying a hotfix, reapply the hotfix.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;March 2017</p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines</div>