#1 Global Leader in Data Resilience

SureBackup fails: Failed to call RPC function - Access is Denied

KB ID: 1478
Product: Veeam Backup & Replication
Published: 2012-01-20
Last Modified: 2025-01-02
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When the Veeam vPower NFS Service on the Mount Server used by the SureBackup job is set to use any account other than , and that account is not a member of the Local Administrator user group, the SureBackup job will fail with errors similar to:

Error: Failed to call RPC function 'AddConnection': Access is denied. Failed to create registry key [SOFTWARE\VeeaM\Veeam NFS\Connections\04dda549-aeac-422e-9534-d06592fef6f6]. RPC: Failed AddConnection.
The situation described in this article rarely happens because, by default, the Veeam vPower NFS Service service is run using the 'Local System' account.

Cause

The access is denied error occurs because the account that the Veeam vPower NFS Service service is set to use for 'Log On As' is not set to Local System and assigned account is not a member of the Local Administrators user group.

Solution

Review the Services (services.msc) running on the Veeam Backup Server and associated managed servers (proxies, repositories, etc.), and set the services to 'Log On As' Local System. This is the default configuration for all Veeam-named services.

 

The only exception to using the Local System account for running the Veeam named services is when the VeeamBackup configuration database is hosted by a Microsoft SQL Server instance running on a remote server. In such a configuration, only the following services are modified to use a domain account to allow access to the configuration database on the remote SQL server:

  • Veeam Backup Server RESTful API Service
  • Veeam Backup Service
  • Veeam Broker Service
  • Veeam CDP Coordinator Service
  • Veeam Cloud Connect Service
  • Veeam Guest Catalog Service
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Veeam Backup & Replication
Veeam Data Cloud for Microsoft 365
Veeam Data Cloud for Microsoft Entra ID
Veeam Data Cloud for Salesforce
Veeam Data Cloud for Microsoft Azure
Veeam Data Cloud Vault
Veeam Backup for Microsoft 365
Veeam Backup for Microsoft Entra ID
Veeam Backup for Salesforce
Veeam ONE
Veeam Service Provider Console
Veeam Agent for Microsoft Windows
Veeam Agent for Linux
Veeam Backup for Nutanix AHV
Veeam Backup for AWS
Veeam Backup for Microsoft Azure
Veeam Backup for Google Cloud
Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
Veeam Management Pack for Microsoft System Center
Veeam Recovery Orchestrator
Veeam Agent for Mac
Veeam Agent for IBM AIX
Veeam Agent for Oracle Solaris
Veeam Cloud Connect
Veeam Kasten for Kubernetes
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.