• 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.

Need latest migration agent

Hello IgorG,

Thanks for your reply again, here is my configuration and the error i am getting.

Destination server:
Windows 2008 64bit
Plesk for Windows 9.3.0
Migration Manager v9.300.3643.12484 (build 091222.05)

Source server:
Windows 2008 64 bit
Please for Windows 9.2.3
Plesk Agent: V9.300.3643.12193


***** error in log *****

== STDOUT ====================
The version of Plesk Migration Agent running on the remote host is older than the version of Plesk Migration Manager being currently used. Please install Plesk Migration Manager components of the same version.
== STDERR ====================

4868: 2010-04-20 08:07:20,236 DEBUG <migration_handler.MigrationGetObjectsListAction object at 0x00A5EAB0>: response
4868: 2010-04-20 08:07:20,236 INFO Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>3003</errcode>
<errmsg>The version of Plesk Migration Agent running on the remote host is older than the version of Plesk Migration Manager being currently used. Please install Plesk Migration Manager components of the same version.</errmsg>
</response>
 
Do you have the same 9.3.0 migration agent installed on both servers?
 
Try to install the same migration agent on both servers.
 
Hi IgorG,

installed same agent on both server, still same message.

Thanks,
Farooq

hi,

yes i have the exactly same problem. both of them is 9.3 and we installed the same versions. but we see the same error still.

any advices?
 
Contact support team for detailed investigation of this problem directly on your servers.
 
Back
Top