• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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