• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Runtime error: not well-formed (invalid token)

E

EmmanuelJ

Guest
Hello
I try to migrate plesk domain on 8.1 to plesk 9.2. Sometime the migration work ( I select domain by domain) sometime not.
The progress status bar of the migration hang up to 50%, during many hours and I should cancel the migration. The size is not really big (50 Mo)
I didnt' see any information on the logs, but not sure.
So I decide to migrate mannualy the domain.
PleskX.pl -dump-domains=my.site.ch -o -v dump.tar.gz
I transfer the file to 9.2, gunzip dump and rename dump to dump.psa and try to convert the file
usr/local/psa/bin/pre9-backup-convert convert -d /var/lib/psa/dumps/ ./dump.psa
And I have this message:
Runtime error: not well-formed (invalid token): line 2, column 540
I have posted the begining of this file.
Anybody has this same problem ?

Thanks

Content-Transfer-Encoding: binary
Content-Type: multipart/related; boundary="_----------=_1269212939253180-----------------------------------------"
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.73; B3.01; Q3.01)
Date: Mon, 22 Mar 2010 00:08:59 +0100


--_----------=_1269212939253180-----------------------------------------
Content-Disposition: inline; filename="dump.xml"
Content-Length: 10311
Content-Transfer-Encoding: binary
Content-Type: text/xml; name="dump.xml"
 
As I know there was support ticket with similar problem. There was complex investigation and searching reason of this issue. Some complex database intervention also required for fixing this problem. Therefore I can suggest you contact support team for fixing this problem with reference to mentioned ticket ID #764482
 
I have investigate and it's was a problem with custom button and special character not really good supporter by the the plesk migration script.
Thanks for your help.
 
Back
Top