Re: Access Denied etc. - appears to be Server 2003 SP1 problem

I have solved this problem myself, so this message is for the benefit of
Googlers. MS have changed the Service Control Manager (SCM) on
Windows 2003 SP1 so that it has a different ACL. It seems that when you do
use SQL-DMO to query the state of a server, it checks the service state on
the node in question, and if the user doesn't have Connect, Enumerate
Service and Query Lock permissions on the SCM he gets a "Service Control:
Access Denied" message.

The good news is that you can change the ACL on the SCM on SP1 (it was
wired-in previously). The bad news is that I can't find a utility or MMC
snap-in to do this: it seems you have to write a program (which is what I
have done).

N.B. This problem is not confined to SQL clusters


"Graham Morris" <Graywing@xxxxxxxxxxxxxxxx> wrote in message
news:%239BKAoBlFHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
> This now appears to be a problem related to installing Server 2003 SP1 -
> after I uninstalled it the problem went away. Sorry about the wrong info.
> Can anyone help?
>
> "Graham Morris" <Graywing@xxxxxxxxxxxxxxxx> wrote in message
> news:eiu3zA2kFHA.1412@xxxxxxxxxxxxxxxxxxxxxxx
>>I have a two node SQL Server 2000 cluster which I have upgraded to SP4.
>>
>> My application, running as a non-privileged user on another node, now
>> gets an
>> "access denied" error when it tries to check the state of the cluster
>> using SQL-DMO.
>> The code (in VBScript) looks like this:
>>
>> Dim oSQL
>>
>> set oSQL = CreateObject("SQLDMO.SQLServer")
>>
>> oSQL.Name = "VIRTUALSERVER"
>>
>> Dim stat
>>
>> stat = oSQL.Status
>>
>> WScript.echo "Status is " & stat
>>
>>
>> The line stat = oSQL.Status fails with "Access Denied". There is no
>> error if SQL Server is not clustered.
>>
>> The same user in the same environment can successfully run osql and query
>> the database as before.
>> I have an unsatisfactory workaround - if I call oSQL.Connect before
>> checking the status, it works. However if the server is down, it takes
>> 10-15 seconds and the connect fails rather than the status call.
>>
>> The OS is SQL Server 2003 (no service pack)
>>
>>
>
>


.

Relevant Pages

  • RE: SSIS Transfer object failure
    ... The problem is the "CopySchema" option it has to be set to ... a SQL Server 2005 SP1 database table to another database; ... I would like to let you know that though SQL Server ... 2005 SP1 has fixed many known issues, there are still some new discovered ...
    (microsoft.public.sqlserver.dts)
  • Re: SQL Server 2005 faulure when updating to SP1
    ... i have installed Sql Server 2000 SP4 also, ... people to install SP1 on a SQL 2005 Server, ... If you were to look at the permissions on the $4IDR files only the Backup ...
    (microsoft.public.sqlserver.setup)
  • Error creating a new resource
    ... have you apllied a SP1 on SQL server too? ... >I try to create a new resource from Project Professional ... >OPTION or spans a view that specifies WITH CHECK OPTION ...
    (microsoft.public.project.pro_and_server)
  • Re: SQL 2005 Compact Edition and Visual Studio 8 without Service Pack 1
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... no references were placed in the C:\Program ... but the compile ... VS.NET 2005 SP1. ...
    (microsoft.public.sqlserver.ce)
  • Re: Default Service SQL Server 2000
    ... No...Enterprise Manager and Query Analyzer don't control SCM ... The registry is where those settings are stored. ... Is there any way to set this in Enterprise manager or through Query Analyzer ... I have SQL Server 2000 and SQL Server 2005 loaded on my computer. ...
    (microsoft.public.sqlserver.setup)