MS SQL Server security - SQL 2000 SP3 and NT4 Domain Issues

Author

SQL 2000 SP3 and NT4 Domain Issues

Mike Mattix

2005-05-02, 1:23 pm

I am having a couple of problems with my SQL 2000 SP3 installation. I
suspect they are related but really don't know.

My SQL Server Instance keeps losing connection with the NT4 Domain
Controller. I keep getting job errors that claim it cannot determine if
owner (MyDomain\SQLUser) of job XYZ has server access (reason: Could not
obtain information about Windows NT group/user 'MyDomain\SQLUser'. ISQLState
42001 (Error 8198))

The second issue that began about the same time is Integrated Security
access seems to quit after around 4 days of running. First time I rebooted,
the second time I just stopped and restarted SQL Server (I was remote the
second time). Both of these resolved the problem is just reappeared last
Saturday.

Additional information: my company required that we get the servers up to
date on patches so 4 days before the first occurance we installed a boat load
of patches. This is the production machine for a manufacturing site that
runs 24/7/52 so we don't frequently patch the system as it normally will
require a reboot.

I have searched this newsgroup and have found nothing similar and as I said
I suspect they are related. If the server cannot validate the credentials of
the job owner it probably cannot validate the credentials of the Integrated
Security Trusted Connection....

Any ideas would be very appreciated.

thanks

Mike

--
Mike Mattix
CP Kelco, Inc
Okmulgee, OK

Jasper Smith

2005-05-02, 8:23 pm

This is actually pretty common. The sure fire way to eliminate this issue is
to set the job owner to sa.
Also see http://support.microsoft.com/defaul...b;en-us;q241643

--
HTH

Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org

"Mike Mattix" < MikeMattix@discussio
ns.microsoft.com> wrote in message
news:6CF3EF95-5BC9-426C-A4CD- 41DF8DF24506@microso
ft.com...
>I am having a couple of problems with my SQL 2000 SP3 installation. I
> suspect they are related but really don't know.
>
> My SQL Server Instance keeps losing connection with the NT4 Domain
> Controller. I keep getting job errors that claim it cannot determine if
> owner (MyDomain\SQLUser) of job XYZ has server access (reason: Could not
> obtain information about Windows NT group/user 'MyDomain\SQLUser'.
> ISQLState
> 42001 (Error 8198))
>
> The second issue that began about the same time is Integrated Security
> access seems to quit after around 4 days of running. First time I
> rebooted,
> the second time I just stopped and restarted SQL Server (I was remote the
> second time). Both of these resolved the problem is just reappeared last
> Saturday.
>
> Additional information: my company required that we get the servers up to
> date on patches so 4 days before the first occurance we installed a boat
> load
> of patches. This is the production machine for a manufacturing site that
> runs 24/7/52 so we don't frequently patch the system as it normally will
> require a reboot.
>
> I have searched this newsgroup and have found nothing similar and as I
> said
> I suspect they are related. If the server cannot validate the credentials
> of
> the job owner it probably cannot validate the credentials of the
> Integrated
> Security Trusted Connection....
>
> Any ideas would be very appreciated.
>
> thanks
>
> Mike
>
> --
> Mike Mattix
> CP Kelco, Inc
> Okmulgee, OK

Mike Mattix

2005-05-02, 8:23 pm

Jasper,

That might solve problem 1 but probably does nothing to solve problem 2. I
guess I am confused as to WHY this is common...

I have found a patch that will be included in SP4 (825042) that looks
promising but will reserve comment until I see it working.

I will probably move to using sa as the owner to at least get the jobs
running, that way I can see if I am continuing to have problem 2 before I get
users calling..

thanks

Mike
--
Mike Mattix
CP Kelco, Inc
Okmulgee, OK

"Jasper Smith" wrote:

> This is actually pretty common. The sure fire way to eliminate this issue is
> to set the job owner to sa.
> Also see http://support.microsoft.com/defaul...b;en-us;q241643
>
> --
> HTH
>
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Mike Mattix" < MikeMattix@discussio
ns.microsoft.com> wrote in message
> news:6CF3EF95-5BC9-426C-A4CD- 41DF8DF24506@microso
ft.com...
>
>
>

Jasper Smith

2005-05-02, 8:23 pm

Using Named Pipes rather than TCP/IP might sort problem 2. If it recoccurs
it would be worth trying to diagnose whether both TCP/IP and NP connections
are affected (you can force the protocol using osql or QA by specifying it
in the servername e.g. osql -E -S tcp:servername or osql -E -S
np:servername). Problem 1 is a bug in Windows IIRC which was still there in
Win2k, moving to Windows 2003 would no doubt help. As for problem 2 again
I'd say this is a windows/domain issue not necessarily related to SQL
Server. These types of transient issues can be pretty tricky to nail down.
If you are hitting issues impacting your production environment I'd suggest
contacting PSS although I can't remember if NT4 is even supported anymore

--
HTH

Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org

"Mike Mattix" < MikeMattix@discussio
ns.microsoft.com> wrote in message
news:1ADED074-A9AA-4AB3-BDBA- 26B3360DA916@microso
ft.com...[color=darkred]
> Jasper,
>
> That might solve problem 1 but probably does nothing to solve problem 2.
> I
> guess I am confused as to WHY this is common...
>
> I have found a patch that will be included in SP4 (825042) that looks
> promising but will reserve comment until I see it working.
>
> I will probably move to using sa as the owner to at least get the jobs
> running, that way I can see if I am continuing to have problem 2 before I
> get
> users calling..
>
> thanks
>
> Mike
> --
> Mike Mattix
> CP Kelco, Inc
> Okmulgee, OK
>
>
> "Jasper Smith" wrote:
>

Sponsored Links