Discussions specific to the VMware vSphere hypervisor
Post Reply
DavidS
Veeam ProPartner
Posts: 11
Liked: 6 times
Joined: Aug 18, 2014 12:00 pm
Full Name: David
Location: Switzerland
Contact:

RPC function call failed. RPC error:Acces is denied

Post by DavidS » Nov 13, 2014 7:32 am 2 people like this post

Hello All

I've encoutered a strange error in Veeam B&R7 and I'd like to share the "solution" with you guys.

Error:

Code: Select all

RPC function call failed. Function name: [IsSnapshotInProgress]. Target machine: [IPv4]. RPC error: Access is denied. Code: 5
Setting:
I set up a job with Guest Processing and Application-aware image processing and the correct credentials (tested)

Solution:
The credentials were in the format "username@domain.local", after I changed it to "domain.local\username" it all worked out well.

I knew, it's stated somewhere that the format should be pre-Windows 2000, but it's not 100% obvious that it can't be username@domain

So if someone is struggling with this error, check the credentials format.

And maybe someone of the veeam team reads this and can give me a plausible reason why the newer format is not supported (or if it ever will be supported).

Greatings
David

Vitaliy S.
Veeam Software
Posts: 21617
Liked: 1290 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: RPC function call failed. RPC error:Acces is denied

Post by Vitaliy S. » Nov 18, 2014 11:51 am

Hi David,

Yes, specifying user credential in this format "username@domain.local" is not supported for AAIP and indexing options. As far as I know it is caused by some incompatibility issues in the API provided by Microsoft (don't have these KBs handy).

Thanks!

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

Re: RPC function call failed. RPC error:Acces is denied

Post by foggy » Nov 18, 2014 11:55 am

Though you can use credentials in UPN format (username@domain.local) for other connections within Veeam B&R, for example, to connect to vCenter Server.

dcph
Lurker
Posts: 1
Liked: never
Joined: Jun 30, 2017 3:54 pm
Full Name: David Ph
Contact:

Re: RPC function call failed. RPC error:Acces is denied

Post by dcph » Jun 30, 2017 4:02 pm

We had the same issue this week with a VM after we performed an in-place upgrade from Server 2003 R2 to Server 2008 R2. We had to disable the firewall service completely and reboot the VM, even though it showed the firewall as disabled for all 3 network profiles. This is more of an issue with the VM and not Veeam. It had been P2V'ed at some point in the past and now we performed an in-place upgrade. We really need to be migrate the application to a new VM.

benbour
Enthusiast
Posts: 35
Liked: 4 times
Joined: May 05, 2015 9:48 pm
Full Name: Ben Bourcier
Contact:

Re: RPC function call failed. RPC error:Acces is denied

Post by benbour » Jul 20, 2017 1:19 pm

Same issue here - Cause was a Microsoft issue when doing in place Domain Controller upgrade (in my case 2012 to 2016). The netlogon service gets set to only start manually.

After changing them back to auto start, Veeam was fine...

Topic here:

https://social.technet.microsoft.com/Fo ... verPreview

Dassy
Lurker
Posts: 1
Liked: never
Joined: May 03, 2018 12:52 pm
Full Name: Daniel Chambers
Contact:

Re: RPC function call failed. RPC error:Acces is denied

Post by Dassy » May 31, 2018 1:18 pm

My issue was that domain authorisation had dropped, adding the device back to the domain resolved this.

Post Reply

Who is online

Users browsing this forum: chris.lokken and 31 guests