I get:
"Access is denied".
I'm able to install in a VISTA workstation and VISTA laptop with now
problem. Has anyone run into this and if so have you found a solution?
Here is part of the log:
2008-08-27 10:18:34 SQLEngine: : Checking Engine checkpoint
'StartEngineService'
2008-08-27 10:18:34 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM
(-mSqlSetup -f -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659
-T3610)...
2008-08-27 10:18:34 Slp: Sco: Attempting to start service MSSQL$SQL2008
2008-08-27 10:18:34 Slp: Sco: Attempting to open SC Manager
2008-08-27 10:18:34 Slp: Sco: Attempting to open service handle for service
MSSQL$SQL2008
2008-08-27 10:18:37 Slp: Sco: Service MSSQL$SQL2008 started
2008-08-27 10:18:37 Slp: Sco: Attempting to close service handle for service
MSSQL$SQL2008
2008-08-27 10:18:37 Slp: Sco: Attempting to close SC Manager
2008-08-27 10:18:37 Slp: Sco: Attempting to get service process id for
service MSSQL$SQL2008
2008-08-27 10:18:37 Slp: Sco: Attempting to open SC Manager
2008-08-27 10:18:37 Slp: Sco: Attempting to open service handle for service
MSSQL$SQL2008
2008-08-27 10:18:37 Slp: Invoking QueryServiceStatusEx Win32 API
2008-08-27 10:18:37 Slp: Sco: Attempting to close service handle for service
MSSQL$SQL2008
2008-08-27 10:18:37 Slp: Sco: Attempting to close SC Manager
2008-08-27 10:18:37 Slp: Sco: Returning service process id 2560
2008-08-27 10:18:37 SQLEngine: : Checking Engine checkpoint
'GetSqlServerProcessHandle'
2008-08-27 10:18:37 SQLEngine: --SqlServerServiceSCM: Waiting for nt event
'Global\sqlserverRecComplete$SQL2008' to be created
2008-08-27 10:18:47 SQLEngine: --SqlServerServiceSCM: Waiting for nt event
'Global\sqlserverRecComplete$SQL2008' or sql process handle to be signaled
2008-08-27 10:18:47 Slp: Configuration action failed for feature
SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2008-08-27 10:18:47 Slp: Access is denied
I'll work on it as soon as I have some spare time and let you guys know
what's I find even if positive or negative.
--
Ekrem Önsoy
"ProfDHDorr" <ProfD...@discussions.microsoft.com> wrote in message
news:6A9FC7E1-1E36-42C3...@microsoft.com...
--
Ekrem Önsoy
"ProfGHDorr" <ProfG...@discussions.microsoft.com> wrote in message
news:976D5358-2F9B-40CE...@microsoft.com...
Installation succeeds, no problem at all.
So, this must not be a general error that everyone can meet. There must be
something particular about your environment.
--
Ekrem Önsoy
"ProfDHDorr" <ProfD...@discussions.microsoft.com> wrote in message
news:6A9FC7E1-1E36-42C3...@microsoft.com...
Did you find a solution to the 'access denied' issue when installing? I
have encountered the same issue installing SQL 2008 Developer Edition on
Windows XP Profession SP2. I have installed successfully on Windows Vista
Ultimate.
Thanks.
However, the cause may be the same. SQL Server 2008 requires that the account doing the install is assigned to the local policy option called debug. For some reason sql server needs to know that it has completed an initial build with whatever comes from microsoft. I can see that a sql server started and stopped. It's while waiting for the start up of the second time that the installation process checks to see if sql server is running. To do this the sql server installer needs this local policy debug option.
Hopefully you will get an email reminder about this post.
> On Wednesday, August 27, 2008 10:50 AM ProfDHDor wrote:
> No matter how I log into my work station and with every security
> configuration that I've tried, I always get the same error when attempting to
> install SQL Server 2008 on XP SP3. It happens at:
> SqlEngineDBStartConfigAction_install.configss_cpu32
>
> I get:
>
> "Access is denied".
>
> I'm able to install in a VISTA workstation and VISTA laptop with now
> problem. Has anyone run into this and if so have you found a solution?
>>> On Wednesday, August 27, 2008 3:59 PM ekre wrote:
>>> I'm setting up an environment to test this issue as I've seen some others
>>> also complain about this "Access is denied" error and the interesting thing
>>> here is that every one who complains has Windows XP with SP3. I suspect SP3
>>> has something to do with this problem. I've just read what's new with SP3
>>> and that White Paper was just an overview.
>>>
>>> I'll work on it as soon as I have some spare time and let you guys know
>>> what's I find even if positive or negative.
>>>
>>> --
>>> Ekrem Önsoy
>>>
>>>
>>>
>>> "ProfDHDorr" <ProfD...@discussions.microsoft.com> wrote in message
>>> news:6A9FC7E1-1E36-42C3...@microsoft.com...
>>>> On Wednesday, August 27, 2008 4:46 PM ProfGHDor wrote:
>>>> Just so you know, this was happening with SP 2 as well. I updated to SP 3 to
>>>> see if it would make a difference and it did not.
>>>>
>>>> "Ekrem Önsoy" wrote:
>>>>> On Wednesday, August 27, 2008 5:25 PM ekre wrote:
>>>>> OK, I noted it.
>>>>>
>>>>> --
>>>>> Ekrem Önsoy
>>>>>> On Thursday, August 28, 2008 4:19 PM ekre wrote:
>>>>>> My test environment:
>>>>>> OS: Windows XP wth SP3
>>>>>> SQL Server: SQL Server 2008 Express Edition with Tools
>>>>>>
>>>>>> Installation succeeds, no problem at all.
>>>>>>
>>>>>> So, this must not be a general error that everyone can meet. There must be
>>>>>> something particular about your environment.
>>>>>>
>>>>>> --
>>>>>> Ekrem Önsoy
>>>>>>
>>>>>>
>>>>>>
>>>>>> "ProfDHDorr" <ProfD...@discussions.microsoft.com> wrote in message
>>>>>> news:6A9FC7E1-1E36-42C3...@microsoft.com...
>>>>>>> On Saturday, September 06, 2008 2:44 AM apachej wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Did you find a solution to the 'access denied' issue when installing? I
>>>>>>> have encountered the same issue installing SQL 2008 Developer Edition on
>>>>>>> Windows XP Profession SP2. I have installed successfully on Windows Vista
>>>>>>> Ultimate.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> "ProfGHDorr" wrote:
>>>>>>>> On Tuesday, July 21, 2009 6:49 AM Hamzakutty PK wrote:
>>>>>>>> You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.
I agree with with Jim, adding the debug user to the local policy does
help.