• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Resolved Plesk Migration Extension Fails with List Object Error

technabob

New Pleskian
I'm attempting to migrate several websites (all under a single subscription) from one Plesk server (Both running Onyx 17.5.3) to another using the Migration Extension (version 2.10.10-0).

However, every time I attempt to run the migration, I get the following error:

Error: Plesk Migrator returned non-zero exit code COMMAND: '/usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator' 'add-task' '/usr/local/psa/var/modules/panel-migrator/sessions/20170722154640/config.ini' '--command-file' '/usr/local/psa/var/modules/panel-migrator/sessions/20170722154640/new-task-command.json' '--migration-list-file' '/usr/local/psa/var/modules/panel-migrator/sessions/20170722154640/migration-list.json' '--task-id' '2017-07-22-15-47-48' EXIT CODE: 1 STDOUT: [2017-07-22 15:47:49][INFO] Initialize Plesk Migrator [2017-07-22 15:47:49][INFO] Target Plesk host: 216.70.112.58 [2017-07-22 15:47:49][INFO] Source Plesk 'source' host: 64.207.153.49 [2017-07-22 15:47:49][INFO] Target Plesk host: 216.70.112.58 [2017-07-22 15:47:49][ERROR] Failed to add new migration task Cause: 'list' object has no attribute 'iteritems' That is a critical error, migration was stopped. STDERR:

Any help would be greatly appreciated, as I'm under the gun to complete this migration in the next couple of days, and I'd rather not have to manually migrate everything.
 
Thanks UFHH01. I actually managed to solve the problem myself. I used advanced mode, and watched the progress of the migration logs on the server, and realized that the destination server had its IP set to Dedicated instead of Shared, which was the root cause.
 
Back
Top