#1 Global Leader in Data Resilience

Not all privileges or groups referenced are assigned to the caller

KB ID: 2465
Product: Veeam Backup & Replication
Veeam ONE
Veeam Service Provider Console
Veeam Recovery Orchestrator
Veeam Cloud Connect
Published: 2018-03-26
Last Modified: 2024-02-22
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 upgrading, the installer encounters the following error message which prevents it from proceeding:

 “Not all privileges or groups referenced are assigned to the caller”
Not all privileges or groups referenced are assigned to the caller

Cause

This error is typically caused by permission or assignment issues within the Global Policy settings. Specifically, it may occur when the Debug Programs policy is not applied to the account being used to execute the installer.

Solution

  1. Open Run and type in 'secpol.msc' to bring up the Local Security Policies.
  2. Navigate to Security Settings > Local Policies > User Rights Assignment and locate the policy for “Debug programs”​
  3. Right-click the "Debug programs" policy and select "Properties."
  4. Ensure that the account used to run the installer is listed in the "Local Security Setting" tab, or included in one of the groups listed.
  5. Any changes made to the Security Settings will only take effect after the affected user account signs off and logs back in.
Defaults
Example of Default Settings

More Information

If the account being used to run the installer does not have the 'Debug programs' security setting, it can cause the fresh install of Veeam ONE or Veeam Service Provider Console to fail during the 'Installing Microsoft SQL Server Express' stage. In this case, the installer may not display the error message mentioned above. Instead, it fails with the message 'Setup Failed'.

If you encounter this issue, running the SQL Express installer on its own may display the following prerequisite error:

Rule "Setup account privileges" failed.
The account that is running SQL Server Setup does not have
one or all of the following rights: the right to back up files
and directories, the right to manage auditing and the security
log and the right to debug programs. To continue, use an
account with both of these rights. For more information, see
http://msdn.microsoft.com/en-us/library/ms813696.aspx,
http://msdn.microsoft.com/en-us/library/ms813959.aspx and
http://msdn.microsoft.com/en-us/library/ms813847.aspx.
SQL Install Failure
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

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.