• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 539
  • Last Modified:

SQL server Installation Failed with Error "Access is denied"

Hello, I'm installing SQL Server 2008r2 on a Windows Server 2008 R2 standard.  I've all the users rights needed on Back up files and directories, Bypass traverse checking ,Debug programs, Lock pages in memory and Manage auditing and security log. Below is the error i'm receiving: please see the attachment.
1 Solution
PadawanDBAOperational DBACommented:
I don't see an attachment.
David ToddSenior DBACommented:

Suggest that you need to run as Administrator for the installation.

There are many of the problems for this. As there are no attachments but like i can only say as if that there can be an administrative issues for the same. Here can be a solutions for you..

 Here is a solution for this.

This failure often is caused by a system or domain policy removing the SeDebugPrivelege security privilege from the administrator account running setup. Verify that the account running has this privilege.

The AccessChk tool will print all privleges for an account (http://technet.microsoft.com/en-us/sysinternals/bb664922.aspx) by running:
accesschk.exe -a <Domain>\<Account> *

Alternatively, we can check this through your group policy editor as mentioned below:

Open Group Policy...
 Start | Run | Type: gpedit.msc | OK |
Navigate to
 Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs

The account through which we are trying to run the setup should be here ( besides the local admin on that machine). I included that here, restarted the server ( this is mandatory, gpupdate /force will not work) and ran the setup and it was successful this time.

SQL Server 2008 setup needs this privilege to start up the SQL Server process and listen to an event that signals back to setup that SQL Server successfully started.

In addition please refer these link for the references...



angel7170Author Commented:
I found the exact same information on google and just by restarting the server solve the issue.  Well definitely you need to have all the necessary permissions and rights but those doesn't reflect until you restart the server.

Thank you!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now