• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Connection to host is not available or migration agent is not running on the source h

Pickaweb_Support

New Pleskian
Hello

I am trying to migrate a plesk 9.5 to plesk 11.5 but I always get same issue

I can connect to source host using Share & File on Windows :
\\IP\c$ -> its okay
Firewall is off on both servers

How could I solve it?

Best Regards
Alan.
 
More information. please help :(

[2014-01-03 03:59:05.259|3456] ERROR: Launchpad could not send scout: Subprocess <subprocess[5108] 'C:\\Program Files (x86)\\Parallels\\Plesk\\PMM\\Migration\\migrmng --deploy-scout --host=SERVER --login=Administrator --password=XXXXXXXXXX --session-path=C:\\Program Files (x86)\\Parallels\\Plesk\\PMM\\msessions\\2014010303590485 --dumps-dir=C:\\temp\\2014010303590485 --system-type=windows'> was finished with exit code 12
== STDOUT ====================
<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error">
<message severity="error">
<description />
<message severity="error">
<description>Expected shared key from server.</description>
</message>
</message>
</execution-result>
== STDERR ====================

[2014-01-03 03:59:05.259|3456] DEBUG: <migration_handler.MigrationGetScoutInfoAction object at 0x022A6ED0>: response
[2014-01-03 03:59:05.259|3456] INFO: Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>3012</errcode>
<errmsg>Connection to host is not available or migration agent is not running on the source host</errmsg>
</response>
 
This seems to issue that with migration agent communication. Try installation same version of Migration agent on both side. Try installing 11.5 on both side and check whether they are able do the job for you..
 
Back
Top