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

We are also having this problem with our 2003 SP1 SQL servers. Can you
provide or point me to a examples of source code for your custom program?

"Graham Morris" wrote:

> 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: Error 3146 (VB6)
    ... Using DAO 3.6, the problem occurs. ... part of the problem - but of course that also runs the risk of query never ... VB and somehow automating MSAccess, ... Normally when we have to use multiple SQL Servers for a query - we do it ...
    (microsoft.public.vb.database.dao)
  • moving data between servers
    ... I have a query on the best way for moving data across the SQL Servers. ... the data in a dataset and use it's WriteXML method to generate an XML file. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: major bug in SQL 2000
    ... If you post a complete repro script, we can try it on our SQL Servers and see if it reproduces... ... "Franc v/d Westelaken" wrote in message ... >>design manager ... but when you open the query it ...
    (microsoft.public.sqlserver.server)
  • RE: Query execution plan different between production/test - same data
    ... The same query can behave differently on different boxes ... have the same kind of data and data distribution? ... * How often are statistics updated on the good and bad sql servers? ...
    (microsoft.public.sqlserver.server)
  • Re: SQL 2005 Mailing Error
    ... like SP1 addresses the problem. ... an email will be sent out via database mail. ... Whenever it tries to send an email it fails with this error: ... I have other SQL Servers that use this job fine but they are on SP1. ...
    (microsoft.public.sqlserver.connect)
Loading