Symptoms
- Migration fails with:
PLESK_ERROR: Failed to deploy subscription ‘example.com’
Migration for that subscription is considered completely failed. No further actions are performed for it.
Migration tools tried to perform operation in 3 attempts: Unable to create subscription ‘example.com’.
Command LANG=en_US.UTF-8 ALLOW_WEAK_PASSWORDS=1 PLESK_RESTORE_MODE=1 PSA_PASSWORD=***hidden*** subscription –create example.com -hosting true -hst_type phys -login john -passwd ***hidden*** -ip 192.0.2.2 -do-not-apply-skeleton -notify false -admin-description “some description” -guid 04EEAE9E-E3F7-4790-BFC6-FBC6B2080687 -creation-date 2014-07-02 -ignore-nonexistent-options failed with exit code 1:
stdout:
stderr: Wrong syntax for command’s ‘-passwd’ parameter. Validation failed. The password does not meet password policy requirements because it is too short. - Minimum password length greater than 10 characters in Local Security Policy > Security Settings > Account Policies > Password Policy on destination server
- Password of system user john of example.com on the source server is greater than 10 characters.
Cause
During migration Plesk migrator generates a temporary password for system user equal to 10 characters that is shorter then allowed by Password Policy on destination server. It’s a bug PMT-4663 that will be fixed in further Plesk Migrator updates.
Resolution
As a workaround Login to the destination server via RDP and decrease Minimum password length to 10 or less characters in Local Security Policy > Security Settings > Account Policies > Password Policy. It ca be increased back after migration.
