Free appointment

Documentation
Back to

-603 / -620 Push file from client to server error

Below is a list of possible root causes of your problem with workarounds:

  1. When backing up a Hyper-V cluster, make sure that you use a single central backup system (at least a Windows 10 system as operating system requirement for ActiveImage Protector HyperAgent), where all Hyper-V nodes used in the Hyper-V cluster are entered in the backup software (in ActiveImage Protector HyperAgent can be found under "Settings" > "HyperAgent" > "Hypervisor"). 
  2. This allows automatic detection when virtual machines are assigned to another Hyper-V node. If the backup software is installed locally on each Hyper-V node and the locally assigned virtual machines are selected for backup, this cannot be guaranteed.
  3. Log on to the affected Hyper-V hosts (e.g. via Windows remote access) and uninstall the small helper program of ActiveImage Protector HyperAgent (you can find it in the Control Panel under "Uninstall programs" with "ActiveImage Protector ..." which is only a few MB in size). 
  4. After uninstalling the small helper program, start the task manager on the Hyper-V host concerned and check that no process with the name "rcthelper.exe" is listed, if yes kill the process. 
  5. As a last step, search for the file "rcthelper.exe" on the affected Hyper-V host under this path "C:\Windows\Temp\", if you find the file (which is normally stored in the subfolder "AIP"), then delete this file and all files in the same folder, if present. 
  6. After these two steps are done, manually start the backup in ActiveImage Protector HyperAgent where it failed before, if you still get the error -603 on the first start, click an run the backup a second time.
  7. If VHD/VHDX files are moved or renamed manually, the backup software cannot find the path which was previously stored in the created backup task and the backup fails. In this case, delete the backup task of the affected virtual machine and create this backup task again.
  8. If a Hyper-V checkpoint was deleted manually, the last path in the stored backup task is orphaned. In this case, manually start a full backup of the affected backup task. If an error message "Profile not found" appears, run the full backup manually again.