Failure to install Sql Server 2008 "access is denied"

Question

Hi

 

I am trying to install SQL Server 2008 RC0 but the installation is failing  giving error message as "Access is denied".

 

The installation was performed on a new system having no previous SQL database installed.All the other components of SQL server 2008 were installed except the Database Engine Services.

 

System Configuration:

OS: Windows XP

Hardware : AMD x64

 

Log file error:

 

2008-07-09 10:18:01 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle'
2008-07-09 10:18:01 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete' to be created
2008-07-09 10:18:04 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete' or sql process handle to be signaled
2008-07-09 10:18:04 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2008-07-09 10:18:04 Slp: Access is denied
2008-07-09 10:18:04 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2008-07-09 10:18:04 Slp: System.ComponentModel.Win32Exception: Access is denied
2008-07-09 10:18:04 Slp:    at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
2008-07-09 10:18:04 Slp:    at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
2008-07-09 10:18:04 Slp:    at System.Diagnostics.Process.OpenProcessHandle()
2008-07-09 10:18:04 Slp:    at System.Diagnostics.Process.get_Handle()
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerStartup.StartSQLServerForInstall(String sqlCollation, String masterFullPath, String instanceName, Boolean isConfiguringTemplateDBs, Boolean useSharedMemoryOnly)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2008-07-09 10:18:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2008-07-09 10:18:04 Slp: Exception: System.ComponentModel.Win32Exception.
2008-07-09 10:18:04 Slp: Source: System.
2008-07-09 10:18:04 Slp: Message: Access is denied.
2008-07-09 10:18:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080709_100401\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2008-07-09 10:18:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080709_100401\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2008-07-09 10:18:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080709_100401\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2008-07-09 10:18:26 Slp: Access is denied
2008-07-09 10:18:26 Slp: Watson bucket for exception based failure has been created
2008-07-09 10:19:54 Slp: Completed Action: SqlEngineDBStartConfigAction_install_configrc_Cpu32, returned False

 

 

  Abhijit Banerjee

 

 

 

 

Answer 1

Does anyone have any idea what might be going on here?  I am getting the same error...it doesn't make sense to me.

Answer 2

Sounds like the same issue in this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3660987&SiteID=1

Answer 3

I think I have that part setup properly, and am still getting the error.  If I email you the error file, can you take a look at it?  I'm really at the end of my rope on this one.  I'd hope to start writing SQL Server articles on 2008 long before now, but haven't been table to get it installed correctly.  I'd really appreciate it.

Tim

Answer 4

Hi

 

I'm curious to know if you ever found a resolution for this issue as I'm experiencing the same problem on a Windows 2003 SP2 box.

 

Thanks

 

Answer 5

 

I have the same problem. I am installing SQL Server 2008 on a virtual XP server that is not connected to the internet.

Answer 6

Have anyone found the solution for this ?

 

I am trying to install SQL Server 2008 (with latest release) on Windows Server 2003 server, both enterprise version.

 

Regards

Answer 7

 

Can you open a connect bug with the setup logs attached so we can take a look?

Answer 8

 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.

Answer 9

Thanks for this solution. I will file an issue for us to determine if we can create a rule to catch this issue.

Thanks,
Peter Saddow [Microsoft]

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 10

This worked like a charm.  Thank you very, very much for posting this solution!

Answer 11

@ Prashant Thakwani

You are the Cat's "Meow"

"This worked like a charm.  Thank you very, very much for posting this solution!" Ditto

Answer 12

This is great tip! Thank very much!

Answer 13

@ Prashant Thakwani


Cheers dude......."This worked like a charm.  Thank you very, very much for posting this solution!" Ditto

Answer 14

Prashant,

You are my hero!  I've struggled with this for 3 full days and your solution worked perfectly!

Thanx.

Answer 15

A perfect solution to one of the worst Microsoft errors...
I have struggled around half a day, installing and un-installing like 3 times before I ended up at your blog..

I was wondering if this error can pop up on even Windows Server 2008 too.. ??

Thanks & Regards
Praveen Behara

---

praveen

Answer 16

Hi,

I'm encountering the same error.  Under Debug programs (In GPEDIT.MSC), i already have DB2ADMNS which means my DB2 9.7 client is using a similar feature.  Post installation of DB2 client we had a message box instructing us to manually add DB2USERS and DB2ADMNS in appropriate role like admin role or user role in "Users and Groups".

But in the case of MS SQL server 2008, the installation produces "Access Denied" error  somewhere near 80% of installation and does not proceed.  We are struck there only.  As per the earlier advice to add the installing user id to Debug programs item in gpedit, we did.  But once the box is restarted or any Active Directory refresh happens, this setting in Debug Programs is wiped off (Of course except DB2ADMNS)

So MS has to plan and give a solution for this.

Thanks

RV

Answer 17

I still get the same error message after adding the privileges to the security settings. I am running Window 7.

Could you please assist?

Thanks,

Wayne Roberts 

Answer 18

But once the box is restarted or any Active Directory refresh happens, this setting in Debug Programs is wiped off (Of course except DB2ADMNS)

So MS has to plan and give a solution for this.

Actually Microsoft does not need to plan and have solution for it, rather you need your sysadmins to make sure that the privilege gets added permanently to the user on that box. At least untill the install is finished. Than in your sql install checklist you make sure you add an entry to check this before the install. I'm sure you have a checklist of some sort already.

Jack

Answer 19

 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.

http://support.microsoft.com/kb/2000257

---

Balmukund Lakhani | Please mark solved if I've answered your question
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog: http://blogs.msdn.com/blakhani
Team Blog: http://blogs.msdn.com/sqlserverfaq

Answer 20

Hi,

The location "Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs" is locked/greyed and i could not add my user id (admin user id).  This is locked by corporate network admin.  Inspite of the same setting i see for other users it is getting installed but fails for me and couple of other users only.

Access check gave error stating it could not enumerate files.

Thanks for your help.

Venkat

Answer 21

RRV, I ran into the same problem.   Big Brother Corporate GPO.  But to work around this, in Computer Management, under Local Users and Groups, open Groups and then open the DebugPrograms group.  Add the account(s) you will be using to install into this group.  This DebugPrograms group is by default added to the User Rights Assignment\Debug programs.

 

Logout of the machine, login as the computer account you added to the DebugPrograms group and install the application.  this worked for me

 

Good Luck!

 

thanks to the forum for leading me towards the solution, even though Corporate policies offered a slight initial hurdle.

-dave

Answer 22

Prashant your a start *** 

It worked !! I was stuck for 2 days on this install I added my login, Domain Computers and the SQL service account 

Thanks a lot :)

Answer 23

Don't forget to restart after changing the policy settings! (That cost me another 30 min or so... : \)

Thanks Prashant!

Answer 24

 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.

I failed to start my local service of SQL server, this solution works, thanks.