#1 Global Leader in Data Resilience

VDDK Error 3014 - Insufficient permissions in the host operating system

KB ID: 1937
Product: Veeam Backup & Replication
Published: 2014-10-14
Last Modified: 2025-03-28
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

A Veeam Backup & Replication task interacting with a VMware environment fails with error:

Error --tr:VDDK error: 3014 (Insufficient permissions in the host operating system). Value: 0x0000000000000bc6

Cause

This error occurs when the account used to communicate with the vCenter does not have sufficient permissions.

Solution

This Solution section assumes that a vCenter account with granular permissions is being used by Veeam Backup & Replication. If the account used by Veeam Backup & Replication when the error occurred was the Administrator account (e.g., administrator@vsphere.local), gather logs and create a Veeam Support case.

Ensure that the account used by Veeam Backup & Replication to communicate with the vCenter Server has the required administrative permissions. See the Required Permissions Reference guide.

 

Troubleshooting

To isolate whether this error is caused by the permissions of the account used by Veeam Backup & Replication, edit the vCenter entry and temporarily assign the Administrator (administrator@vsphere.local) account.

If the error (VDDK Error 3014) ceases to occur when using the global Administrator account, this indicates that the previously used account had missing permissions.

  • Review the Required Permissions Reference guide and ensure that the account intended to be used by Veeam Backup & Replication has been configured appropriately.
  • Review the vCenter environment and ensure that the account permissions are being propagated to all objects within the environment.

If the error (VDDK Error 3014) continues to occur when using the global Administrator account, please gather logs and create a Veeam Support case.

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.