Article ID: 124217, created on Jan 18, 2015, last review on May 6, 2016

  • Applies to:
  • Plesk 12.0 for Linux
  • Plesk 11.5 for Linux


Migration fails with the following 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">
            <password type="plain"><![CDATA[******************]]></password>


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.


  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.

Search Words

/usr/local/psa/PMM/var/20150518143337724/domains/ not well-formed (invalid token)

/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)

Migration between two Plesk Hosting.

not well-formed (invalid token)

migration plesk to plesk

That is a critical error, migration was stopped.

29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF