Comprehensive data protection for all workloads
Post Reply
ehammons
Lurker
Posts: 2
Liked: never
Joined: Oct 01, 2013 1:21 pm
Full Name: Eric Hammons
Contact:

Error: Client error:Failed to send command

Post by 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
Chief Product Officer
Posts: 31460
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Error: Client error:Failed to send command

Post by 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
Lurker
Posts: 2
Liked: never
Joined: Oct 01, 2013 1:21 pm
Full Name: Eric Hammons
Contact:

Re: Error: Client error:Failed to send command

Post by 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
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Error: Client error:Failed to send command

Post by foggy »

That's not valid, actually. Hotadd perfectly works with v7 32bit proxies. Not sure what this recommendation is based on.
LHSeattle
Service Provider
Posts: 2
Liked: 2 times
Joined: Oct 18, 2012 4:26 pm
Full Name: Brett Larson
Contact:

Re: Error: Client error:Failed to send command

Post by LHSeattle » 2 people like this post

Renaming/removing the VeeamGuestAgent.exe in the Windows\Temp\VeeamVSSSupport folder to resolve the issue for us.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Error: Client error:Failed to send command

Post by foggy »

Brett, thanks for sharing, much appreciated!
VenoX
Influencer
Posts: 11
Liked: 1 time
Joined: Mar 12, 2012 11:29 am
Full Name: L33t rul0r
Contact:

Re: Error: Client error:Failed to send command

Post by VenoX » 1 person likes this post

Support Case ID: 00468762
The Problem did not dissapear after removing the file.
Opend a Support case and will Keep you informed.
VenoX
Influencer
Posts: 11
Liked: 1 time
Joined: Mar 12, 2012 11:29 am
Full Name: L33t rul0r
Contact:

Re: Error: Client error:Failed to send command

Post by 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
Influencer
Posts: 11
Liked: 1 time
Joined: Mar 12, 2012 11:29 am
Full Name: L33t rul0r
Contact:

Re: Error: Client error:Failed to send command

Post by VenoX »

Still no Solution - replication is not working for more than a week now. I really like veeam but this is dissapointing.
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Error: Client error:Failed to send command

Post by Vitaliy S. »

What does our support engineer say on this? Still investigating?
rchwanim
Lurker
Posts: 2
Liked: never
Joined: May 19, 2014 5:58 pm
Full Name: Mohamad rachwani
Contact:

Re: Error: Client error:Failed to send command

Post by rchwanim »

Try to run the backup with active full
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 269 guests