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

Client does not exist, but is expected to

D

dennis00

Guest
This isg like the 3rd time I have this issue with one of my servers. I currently manage 20 Plesk webhosting servers.

This is the third time I am facing this issue, and it was three times on a different server. Unfortuneatly the last time was more than half a year ago and my memory doesn't reach that far.

I am trying to transfer a domain on a dedicated server from a client of mine to a reseller account on a different Plesk-server. I can perfectly select the domains(4) I wish to migrate. It will backup the files and send them to the other server. Yet while restoring or after restoring it gives the message "Client xxx does not exist, but is expected to".

The issue seems to be related to the source server, as moving any domain to a different server using the migration manager gives issues. No matter which domain I select on the source server and no matter which client I select on the other server. Issues remain.

Does anybody have these experiences and was able to solve this issue?
 
Hi,

try to update Plesk on destination node to latest one. Also, look in migration.log in /usr/local/psa/PMM/var for more information. There should be some useful clues. If neither of this help -- yell support ;)
 
Back
Top