Discussions specific to the VMware vSphere hypervisor
Post Reply
datamek1
Lurker
Posts: 1
Liked: 2 times
Joined: Oct 27, 2011 6:51 am
Contact:

blobcall stub error 1783 post v8 upgrade

Post by datamek1 » Dec 02, 2014 5:07 pm 2 people like this post

Hi All,

Ive been searching most everywhere for a solution to this and created an incident for it which lead nowhere other than some level 1 tech saying it was basically all windows rpc service fault (which was probably in her manuscript, but still completely unhelpful).

Anyway, my problem was this when using application aware backups after we upgraded from v7 to v8:

Code: Select all

12/2/2014 5:37:27 PM :: VSSControl: FinishSnapshot failed
Failed to execute VIX command: [RPC function call failed. Function name: [BlobCall].
RPC error:The stub received bad data.
 Code: 1783]. 
When application aware backup was turned off, these machines got backed up just fine.

The usual suspects, restarting vmware tools, checking whether logins where actually assigned after the upgrade, double/triple checking logins, making sure vmware tools where all up to date, rebooting VMs etc etc.. all of them made absolutely no difference.

What did in the end work was deleting the VeeamVssSupport service (sc delete VeeamVssSupport from a prompt with priviledges).

After that everything worked as expected (i didn't need to reboot the VMs after this change).

We had this happen on 5 or 6 machines post the upgrade, some exchange, some mssql and one AD server, so there doesn't appear to be a clear pattern.

So heres to hoping this gets picked up by a google bot so you don't have to waste your time finding a solution.

Regards,
Steffen

Vitaliy S.
Product Manager
Posts: 22976
Liked: 1555 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by Vitaliy S. » Dec 02, 2014 6:54 pm

Hi Steffen, thanks for sharing your solution with the Community.

patrickl78
Service Provider
Posts: 32
Liked: 7 times
Joined: Jan 09, 2014 11:16 pm
Full Name: Patrick Leonard
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by patrickl78 » Dec 02, 2014 8:24 pm

I've actually had that error message myself on a couple of VM's. Thanks for the post! Hopefully Veeam will identify and fix this before I begin rolling out V8 everywhere.

Thanks,
Patrick

kurt_grootjans
Lurker
Posts: 1
Liked: never
Joined: Jan 14, 2015 1:36 pm
Full Name: Kurt Grootjans
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by kurt_grootjans » Jan 14, 2015 1:40 pm

Hi Stefen,

But are you still able to take an application aware backup after deleting the VSS service from Veeam?

Thanks for the confirmation,

Kurt

foggy
Veeam Software
Posts: 18251
Liked: 1558 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by foggy » Jan 14, 2015 4:40 pm

Yes, it is a run-time process, will be re-deployed on the next job run.

bbertelli
Lurker
Posts: 1
Liked: never
Joined: Nov 02, 2013 4:46 am
Full Name: Bruno Bertelli
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by bbertelli » Jan 26, 2015 10:10 pm

Thanks for sharing. Google did not helped me with this one! You did!

Regards

Bruno

knutho
Service Provider
Posts: 4
Liked: 1 time
Joined: Aug 24, 2012 8:56 am
Full Name: Knut-Håvard Olsen
Location: Vesterålen, Norway
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by knutho » Feb 04, 2015 7:57 am

Thanks a lot!
Got this error on 11 vms after upgrade to v8 yesterday.

--
Knut

br_sc
Novice
Posts: 7
Liked: never
Joined: Mar 23, 2010 11:27 am
Full Name: Michael Briegl
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by br_sc » Mar 12, 2015 8:50 am

Solution works fine, but without a reboot of the affected VM after deleting the service it didn't work for me on the first retry of the job.
Veeam recreated the service, managed to start the service, but its startup type was set to disabled (strange effect, because a disabled service usually cannot be started).
Trying to delete the service again yielded an error 1072, only after rebooting the VM the service disappeared and the job retry succeeded.

gigimen
Lurker
Posts: 1
Liked: 1 time
Joined: Jun 29, 2015 7:14 am
Full Name: luigi menegolo
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by gigimen » Jun 29, 2015 7:30 am 1 person likes this post

I confirm: with Windows 2008 R2 I had to reboot the machine to have the VeeamVssSupport service gone.
Afterwards the backup was OK.

frankive
Service Provider
Posts: 887
Liked: 104 times
Joined: May 14, 2013 8:35 pm
Full Name: Frank Iversen
Location: Norway
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by frankive » Jul 01, 2015 8:46 pm 1 person likes this post

I can confirm that this also fixed the same error on a 2008 R2 terminalserver. I did not have to reboot the computer.

frankive
Service Provider
Posts: 887
Liked: 104 times
Joined: May 14, 2013 8:35 pm
Full Name: Frank Iversen
Location: Norway
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by frankive » Jul 06, 2015 9:22 pm

the error actually came back again on the same virtual server after a few days AFTER a reboot of the server..

veremin
Product Manager
Posts: 16884
Liked: 1433 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by veremin » Jul 07, 2015 6:18 am

It might be worth opening a ticket to find out the root cause of stalled Veeam VSS service. Thanks.

frankive
Service Provider
Posts: 887
Liked: 104 times
Joined: May 14, 2013 8:35 pm
Full Name: Frank Iversen
Location: Norway
Contact:

Re: blobcall stub error 1783 post v8 upgrade

Post by frankive » Jul 16, 2015 1:13 pm

I had a reboot on the VM server at the same time as backup, my bad.. as always.. :)

Post Reply

Who is online

Users browsing this forum: No registered users and 18 guests