- Plesk Onyx for Windows
Note: This article has the reference to the issue with the fix available:
- #PMT-3452 "Migration on Windows could not start if the path to the ‘plesk’ utility was not specified in the PATH variable of the target server."
- Plesk Migrator 2.5 02 March 2017
Initiating a Migration in Plesk fails with the following error:
Error: Plesk Migrator returned non-zero exit code COMMAND: add-queue-task
"C:\Program Files (x86)\Plesk\/var/modules/panel-migrator/sessions/20170210111550/config.ini" --command-file
"C:\Program Files (x86)\Plesk\/var/modules/panel-migrator/sessions/20170210111550\new-task-command.json"
--migration-list-file "C:\Program Files (x86)\Plesk\/var/modules/panel-migrator/sessions/20170210111550\migration-list.json"
--task-id 2017-02-10-17-40-21 EXIT CODE: 1 STDOUT:
[INFO] Initialize Plesk Migrator
[ERROR] Internal Plesk Migrator error: 'Failed to execute local command 'plesk db "SELECT name FROM Modules WHERE name = 'plesk-multi-server'"':
[Error 2] The system cannot find the file specified', migration is aborted. See the traceback in debug log for more information.
The error about finding multiserver is a known cosmetic bug with internal ID #PMT-3452
Go to Windows Control Panel > System and Security > System > Advanced system settings > Environment Variables and check if PATH includes a path to the Plesk utility C:\Program Files (x86)\Plesk\ctl
Add the path if missing and reboot the server.
Re-initiate the Migration.
Note: Path to Plesk utility may differ if Plesk is installed in another location.