Migration is failing: not well-formed (invalid token)

Created:

2016-11-16 13:09:22 UTC

Modified:

2017-01-26 19:37:11 UTC

1

Was this article helpful?


Have more questions?

Submit a request

Migration is failing: not well-formed (invalid token)

Symptoms

Migration fails with the following error:

 Error:

/opt/psa/PMM/var/20140907043200179/resellers/reseller_name/clients/client_name/domains/domain_name/backup_domain_name_info_1409070446.xml:1463:43: not well-formed (invalid token)

Some passwords look like below in this .xml :

# grep password /opt/psa/PMM/var/20140907043200179/resellers/reseller_name/clients/client_name/domains/domain_name/backup_domain_name_info_1409070446.xml
......
<mailuser user-guid="975bf434-4645-51ae-e0e0-27c75afb996a" name="niazi" guid="b269df99-c475-4029-9904-c0356137a760_mn_1997" id="1997" mailbox-quota="-1" owner-guid="b269df99-c475-4029-9904-c0356137a760" forwarding-enabled="false">
<properties>
<password type="plain"><![CDATA[******************]]></password>

Cause

It happens due to symbols in passwords in national encoding. This behavior is considered as a software issue #PPPM-1985 which will be fixed in future Plesk updates.

Workaround

  1. Go to directory on the source or on the destination host where Migration & Transfer Manager stores temporary migration files. (it is shown in error message)

  2. Find affected accounts

    ~# find ./ -name \\*.xml | xargs grep -B3 CDATA | grep -B3 -P -n "[\\x80-\\xFF]" | grep name\\= | awk '{print $4}'
  3. Reset passwords on the source server via Plesk interface for affected user accounts and then restart the migration.

Have more questions? Submit a request
Please sign in to leave a comment.