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

Migratiom From Plesk 8.6.0 to 9.3.0

S.ImanG

New Pleskian
Hello
I want to migrate from Plesk 8.6.0 to 9.3.0 but I get following error:
"Error: 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."

I'm using Migration Manager v9.300.3643.12484 (build 090420.11) and the latest Migration Agent I found is Migration Agent 9.300.3643.12495 (from Plesk website).
The other thing, when I try to Synchronize PMM I get "Error: Errors have occurred during the process of migration agents synchronization." message.
I also attached migration log file

Regards
Iman
 

Attachments

  • Migration.zip
    3.3 KB · Views: 14
Hello
I got same error:
Error: 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.
 
According to your log file there is:

6028: Warning 09/02/2010 06:50:22.400 : WindowsScoutProxy::SelectAgent Exception processed ({0}) ( System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 94.76.212.144:6489

I have tried:

$ telnet 94.76.212.144 6489
Trying 94.76.212.144...
telnet: connect to address 94.76.212.144: Connection refused
$ telnet 94.76.212.144 22
Trying 94.76.212.144...
telnet: connect to address 94.76.212.144: Connection refused
$ telnet 94.76.212.144 80
Trying 94.76.212.144...
Connected to 94.76.212.144.

Maybe it is firewall related issue?
 
Hello
It is a routing issue in data center, they temporarily gave me a new IP (213.175.218.138) that I replaced it to 213._MYIP_.198 in log file(for security reasons).
Then I think I have to tell PMM not to use 94.76.212.144 but how?
 
But why you can't to use correct accessible IP as IP of source server for PMM?
 
Hello
As you can check in log file I used x.x.x.138 IP as source IP address but MMP it self tried to connect to 94.76.212.144 and 94.76.212.144 is not accessible.
 
Not sure that PMM is so smart for selecting IPs in your network randomly. Seems it is defined somewhere or it is something like routing/gateways/etc network related issue.
 
Do both the servers need a migration manager.... or the source server settles just with a migration agent ?
 
Back
Top