• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved windows Plesk Migrator returned non-zero exit code

nethubonline

Regular Pleskian
Hi all,

We tried to use the Plesk GUI interface to do the migration via Plesk Migrator, but it failed. However the migration can be completed by command line successfully. Can someone help?

Procedure to duplicate the problem

1) Click "Migrate" in the Plesk
1581991921221.png


2) The process stucks as below
1581991924130.png


3) If I click "Skip", the error is shown and nothing is migrated:

Error: Plesk Migrator returned non-zero exit code COMMAND: add-task "C:\Program Files (x86)\Plesk\var\modules\panel-migrator\sessions\20200218092939\config.ini" --command-file "C:\Program Files (x86)\Plesk\var\modules\panel-migrator\sessions\20200218092939\new-task-command.json" --migration-list-file "C:\Program Files (x86)\Plesk\var\modules\panel-migrator\sessions\20200218092939\migration-list.json" --task-id 2020-02-18-09-34-24 EXIT CODE: -1 STDOUT:

Error: Plesk Migrator returned non-zero exit code COMMAND: cancel-task "C:\Program Files (x86)\Plesk\var\modules\panel-migrator\sessions\20200218092939\config.ini" --task-id=undefined EXIT CODE: -1 STDOUT:
1581991933605.png


source server
- Microsoft Windows Server 2008 Service Pack 2
- Plesk 12.5.30

target/destination server
- Microsoft Windows Server 2012 R2
- Plesk Obsidian Version 18.0.23
 
Back
Top