Migration fails: Execution result file can not be opened

Created:

2016-11-16 13:11:52 UTC

Modified:

2017-04-24 11:54:55 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Migration fails: Execution result file can not be opened

Applicable to:

  • Plesk 11.0 for Windows
  • Plesk 9.x and below for Windows

Symptoms

  1. Migration ofa domain fails with error:

    Execution result file (C:\\Program Files (x86)\\Parallels\\Plesk\\PMM\\msessions\\20130429174856558\    ransfer.result) can not be opened
  2. In C:\\Program Files (x86)\\Parallels\\Plesk\\PMM\\msessions\\20130429174856558\\Migration.log :

    Error     29/04/2013 08:20:35.265 : 179e34bd-cc16-4dc5-940b-309cd78d5782 '�', hexadecimal value 0x12, is an invalid character. ( System.ArgumentException: '�', hexadecimal value 0x12, is an invalid character.

Cause

DNS records in Plesk database on source server contain unreadable characters added to the resulting XML file during data backup. The error is occurrs while reading this XML file during the restore.

Resolution

  1. Log in to Plesk on the source server.

  2. Create backup of psa database using this article .

  3. Check DNS records for migrated domain:

    <code>
    "%plesk_bin%\\dbclient.exe" --direct-sql --sql="select * from dns_recs where val ='test.com.';"
    </code>
    <pre>id dns_zone_id type host displayHost val displayVal opt time_stamp
    515 43 CNAME ftp.test.com. ftp.test.com. test.com. test.com. 2002-10-30 04:35:23
    516 43 PTR 203.0.113.2 203.0.113.2 test.com. test.com. 24 2002-10-30 02:35:23
    522 43 CNAME lists.test.com. lists.test.com. test.com. ???2all. 2007-12-09 05:33:27
    </pre>
  4. Discover the corrupted data:

    "%plesk_bin%\\dbclient.exe" --direct-sql --sql="select displayVal from dns_recs where val=<domain_id>;"
    displayVal
    ?¦?2all
  5. Delete corrupted records from the database:

    "%plesk_bin%\\dbclient.exe" --direct-sql --sql="delete * from dns_recs where id=<record_id>;"
  6. Log in to Plesk panel on destination server and run the migration again.

  7. When the migration is finished, manually restore the deleted record for the required domain.

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