Error: Client error:Failed to send command

[ehammons]

Just upgraded to v7 and installed patch and all jobs are getting this error. Waiting for a reply from support but thought id throw this out there. #00457025

[Gostev]

Google says you are the first with this error... this usually means we are facing something really simple and straightforward. Like some modules did not upgrade properly for whatever reason (quarantined by antivirus etc). Let's see what support has to say after looking at the debug logs.

[ehammons]

the backup infrastructure proxy server settings had to have the transport mode changed to network due to the proxy not being 64 bit. the hotadd feature will only work currently in v7 on a 64bit machine.

[foggy]

That's not valid, actually. Hotadd perfectly works with v7 32bit proxies. Not sure what this recommendation is based on.

[LHSeattle]

Renaming/removing the VeeamGuestAgent.exe in the Windows\Temp\VeeamVSSSupport folder to resolve the issue for us.

[foggy]

Brett, thanks for sharing, much appreciated!

[VenoX]

Support Case ID: 00468762
The Problem did not dissapear after removing the file.
Opend a Support case and will Keep you informed.

[VenoX]

Today i deleted the replicas and recreated the Job, what i´ve seen is that an old Server (win2003) is woring while the Linux server and the win2008R2 Server Keep failing.

Hope veeam Support Comes up with a solution soon, because currently my replicas are worthless

[VenoX]

Still no Solution - replication is not working for more than a week now. I really like veeam but this is dissapointing.

[Vitaliy S.]

What does our support engineer say on this? Still investigating?

[rchwanim]

Try to run the backup with active full