The solution was more trivial than expected. The error was caused by the
fact that TEMP env. variable contained blank. Once we changed that the
upgrade to sp3a worked OK. The errors in Security log must be generated by
the security enchancements we enabled. I hope in the future Microsoft will
provide more usefull information in the log or in the documentation.
"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
> Tibi, you need to get SP3a on your SQL for it to be supported on Windows
> Server 2003. I have not seen this error, but all you need to do is apply a
> security template that does not lock it down as much. Then apply SP3a,
when
> done, put on your security template.
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
>
http://www.nw-america.com - Clustering
>
> "Tibi Baraboi" <tibi.baraboi@getronics.com> wrote in message
> news:u6gHFf5WEHA.2176@TK2MSFTNGP11.phx.gbl...
> > Hi,
> > We have a W2k3 cluster with a group MSSQL 2000 sp2. Now when we try to
> start
> > the setup for MS SQL sp3a it stops saying that it cannot detect the
satus
> of
> > a service. We have applied a security template which might conflict with
> MS
> > SQL sp 3a.
> > In security log we get message as below :
> >
> > Does anybody encounter such error?
> > Thank you in advance.
> > Tibi Baraboi
> >
> > Event Type: Failure Audit
> > Event Source: Security
> > Event Category: Object Access
> > Event ID: 560
> > Date: 6/26/2004
> > Time: 5:58:07 PM
> > User: NT AUTHORITY\NETWORK SERVICE
> > Computer: SPS3BEBR01
> > Description:
> > Object Open:
> > Object Server: SC Manager
> > Object Type: SERVICE OBJECT
> > Object Name: RemoteAccess
> > Handle ID: -
> > Operation ID: {0,1119191}
> > Process ID: 612
> > Image File Name: C:\WINDOWS\system32\services.exe
> > Primary User Name: SPS3BEBR01$
> > Primary Domain: EXTRANET
> > Primary Logon ID: (0x0,0x3E7)
> > Client User Name: NETWORK SERVICE
> > Client Domain: NT AUTHORITY
> > Client Logon ID: (0x0,0x3E4)
> > Accesses: Query status of service
> >
> > Privileges: -
> > Restricted Sid Count: 0
> > Access Mask: 0x4
> >
> >
> > For more information, see Help and Support Center at
> >
http://go.microsoft.com/fwlink/events.asp. > >
> >
>
>
