Applicable to:
- Plesk for Windows
Symptoms
-
Migration is stuck at the very beginning with starting migration message and nothing is coming up:
-
While trying to reload source server data from the command line on the target server, it finishes successfully:
C:\> "%plesk_dir%\admin\plib\modules\panel-migrator\backend\plesk-migrator.bat" generate-migration-list "C:\Program Files (x86)\Plesk\/var/modules/panel-migrator/sessions/<datetime>/config.ini"
...
[INFO] FINISH: Generate migration list file
[INFO] Perform final clean up -
The
%plesk_dir%\var\modules\panel-migrator\sessions\<datetime>\config.ini
file contains the following information regarding the user credentials for the target server:CONFIG_TEXT: [plesk]
...
windows-username = "admin" -
The specified user does not exist on the target server at Start > Computer Management > Local Users and Groups > Users
Cause
Incorrect build-in administrator user is provided for the migration, however no warning was shown.
This is a Plesk bug #PMT-3961 which is planned to be fixed in future Plesk updates.
Resolution
For migration via the graphical interface:
-
Cancel the current migration session in Tools & Settings > Migration & Transfer Manager.
-
Start a new migration session specifying credentials fo built-in Windows Administrator.
For migration via the command line or via GIU, without finishing the current session:
-
Log in to the target server via RDP.
-
Edit
%plesk_dir%\var\modules\panel-migrator\sessions\<datetime>\config.ini
file with any text editor and replace admin user with the server's built-in administrator login user:CONFIG_TEXT: [plesk]
...
windows-username = "Administrator" -
Log into the Plesk.
-
Go to Tools & Settings > Migration & Transfer Manager and proceed with the migration.
Comments
2 comments
I tried this solution, but then I get the error that login or password is wrong, so the login was probably correct and this solution not?
Hello @Bart Van Sichem,
It is possible that in your case migration hangs due to a different cause.
I can suggest submitting a support request to find the root cause.
Please sign in to leave a comment.