Article ID: 115111, created on Nov 11, 2012, last review on Aug 12, 2014

  • Applies to:
  • Plesk 11.x for Linux
  • Plesk 10.4 for Linux/Unix


Parallels Plesk Panel (PP) migration fails.
In the pmmcli.log, you may find this error:
== STDERR ====================
26154: 2012-11-09 19:53:19,075 CRITICAL PMMUtility exception:
Subprocess <subprocess[26155] '/usr/local/psa/admin/bin/migration-handler --migration-get-objects-list 20121109195240692'> was finished with exit code 1
== STDOUT ====================
<?xml version="1.0" encoding="UTF-8"?>
    <errmsg>Runtime error in migration handler:
&lt;class 'xml.sax._exceptions.SAXParseException'&gt; /usr/local/psa/PMM/msessions/20121109195240692/dump.xml:2072:40: not well-formed (invalid token)
Traceback (most recent call last):
  File "/usr/local/psa/admin/share/migration-handler/", line 1682, in main
    data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
  File "/usr/local/psa/admin/share/migration-handler/", line 1481, in migration_get_objects_list
    return MigrationHandlerActionRunner(MigrationGetObjectsListAction, agent_to_use, migration_session_id).doActivity()
  File "/usr/local/psa/admin/share/migration-handler/", line 100, in doActivity
    result = self.processor.doActivity()
  File "/usr/local/psa/admin/share/migration-handler/", line 344, in doActivity
    objects_list_object = service.getObjectsList(self.__agent_to_use, agent_dir)
  File "/usr/local/psa/admin/share/migration-handler/", line 112, in getObjectsList
    objects_list = self.makeObjectsListFromDump(agent_name)
  File "/usr/local/psa/admin/share/migration-handler/", line 122, in makeObjectsListFromDump
  File "/usr/lib64/python2.6/xml/sax/", line 107, in parse
    xmlreader.IncrementalParser.parse(self, source)
  File "/usr/lib64/python2.6/xml/sax/", line 123, in parse
  File "/usr/lib64/python2.6/xml/sax/", line 211, in feed
  File "/usr/lib64/python2.6/xml/sax/", line 38, in fatalError
    raise exception
SAXParseException: /usr/local/psa/PMM/msessions/20121109195240692/dump.xml:2072:40: not well-formed (invalid token)
== STDERR ====================


Some passwords in the database are corrupted on the source server.


To resolve the issue, repeat the below steps until the backup is created correctly:
1) Create a backup using the PleskX PMM script and get it to the source server by following the first three steps of this article:
1152 [How to] How to migrate Plesk data manually with Plesk Migration Manager
Example command:
[root@server:temporary_migration_directory]#./ -da -nc -d testbackup -vv >/dev/null 2>&1
2) Validate the backup:
[root@server:temporary_migration_directory]# xmllint --schema /usr/local/psa/PMM/plesk.xsd dump.xml
dump.xml:2122: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE7 0x2D 0x9D 0x77
                <password type="plain">5fГdf4d</password>
3) Find out which user is broken (use the line number from the previous command's output -- 2122 in our example):
[root@server:temporary_migration_directory]# cat dump.xml |head -2122|tail -3
            <user is-domain-admin="false" name="mailname@domain.tld" is-built-in="false" contact="mailname" email="mailname@domain.tld" is-legacy-user="false" guid="7d56204f-1493-47a2-97e3-30c9c8cb1722" cr-date="2012-10-24T23:00:41+01:00">
                <password type="plain">5fГdf4d</password>
4) Get the user's password from the mail database:
[root@server:temporary_migration_directory]# /usr/local/psa/admin/bin/mail_auth_view|grep mailname@domain.tld
|                    mailname@domain.tld |     |                             5fdf4d |
5) Update the user's password accordingly in the PP web interface or using the command-line interface.

e8756e9388aeca36710ac39e739b2b37 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 dd0611b6086474193d9bf78e2b293040 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF