• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Migrtaion Manager

G

gyselroth

Guest
dear all

I have a Problem with the Migration Manager.

Some error while applying stylesheet. Check the error reason and try again.n

Please help me.
 
Hello,

Check /usr/local/psa/PMM/logs/ to get detailed error message.
 
Hi Satoriya

I have checked.
here isnt a actual
log file.

More idea?
 
I am having the same problem on all of my RAQ4 servers. Any ideas anyone?
 
The logs are located in /var/psa/PMM/var/"date"

If you have a look in there you will be able to see the logs.
 
same problem -> here my logfiles

migration.log:

[16:22:38|INFO:30504:p.log] deployer started : /usr/local/psa/admin/sbin/deployer --session-path=/usr/local/psa/PMM/var --agent-name=RaQ4 --translate-dump
[16:22:38|DEBG:30504:p.deployer] Translation of /usr/local/psa/PMM/var/dump.xml to /usr/local/psa/PMM/var/dump-plesk.xml requested
[16:22:38|INFO:30504:p.AgentsFactory] Parsing RaQ4
[16:22:38|INFO:30504:p.AgentsFactory] Parsing /usr/local/psa/PMM/agents/RaQ4
[16:22:38|INFO:30504:p.Agent] Agent RaQ4
[16:22:38|INFO:30504:p.Agent] Description: Cobalt Raq4, XTR
[16:22:38|INFO:30504:p.Agent] EntryPoint: RaQ4.pl
[16:22:38|INFO:30504:p.Agent] DocumentType: /usr/local/psa/PMM/agents/RaQ4/control/RaQ4.dtd
[16:22:38|INFO:30504:p.Agent] Stylesheet: /usr/local/psa/PMM/agents/RaQ4/control/RaQ4.xsl
[16:22:38|INFO:30504:p.Agent] Interpreter: perl
[16:22:38|DEBG:30504:p.deployer] Validating dump with /usr/local/psa/PMM/agents/RaQ4/control/RaQ4.dtd
[16:22:38|INFO:30504:p.log] tError_XmlInternal: Some error while applying stylesheet. Check the error reason and try again. [./xml_parse.cpp:295]
[16:22:38|INFO:30504:p.log] deployer finished. Exit code: 0
[16:27:34|INFO: 1691:p.log] deployer started : /usr/local/psa/admin/sbin/deployer --session-path=/usr/local/psa/PMM/var --agent-name=RaQ4 --translate-dump
[16:27:34|DEBG: 1691:p.deployer] Translation of /usr/local/psa/PMM/var/dump.xml to /usr/local/psa/PMM/var/dump-plesk.xml requested
[16:27:34|INFO: 1691:p.AgentsFactory] Parsing RaQ4
[16:27:34|INFO: 1691:p.AgentsFactory] Parsing /usr/local/psa/PMM/agents/RaQ4
[16:27:34|INFO: 1691:p.Agent] Agent RaQ4
[16:27:34|INFO: 1691:p.Agent] Description: Cobalt Raq4, XTR
[16:27:34|INFO: 1691:p.Agent] EntryPoint: RaQ4.pl
[16:27:34|INFO: 1691:p.Agent] DocumentType: /usr/local/psa/PMM/agents/RaQ4/control/RaQ4.dtd
[16:27:34|INFO: 1691:p.Agent] Stylesheet: /usr/local/psa/PMM/agents/RaQ4/control/RaQ4.xsl
[16:27:34|INFO: 1691:p.Agent] Interpreter: perl
[16:27:34|DEBG: 1691:p.deployer] Validating dump with /usr/local/psa/PMM/agents/RaQ4/control/RaQ4.dtd
[16:27:34|INFO: 1691:p.log] tError_XmlInternal: Some error while applying stylesheet. Check the error reason and try again. [./xml_parse.cpp:295]
[16:27:34|INFO: 1691:p.log] deployer finished. Exit code: 0



migration.result:

<?xml version="1.0"?>
<execution-result status="error"><message code="tError_XmlInternal" severity="error"><context>plesk::tXmlDocFromXslt plesk::apply_stylesheet(plesk::tXsltStylesheet&amp;, plesk::tXmlDocument&amp;)</c
ontext><file>./xml_parse.cpp</file><line>295</line><text>Some error while applying stylesheet. Check the error reason and try again.</text></message></execution-result>
 
I have the same problem also with exactly the same entries in the logs, I think that this is a bug caused by the recent upgrade - it would be good to have SWSOFT comment on this.
 
Back
Top