Re: SQL 2000 SP3 and NT4 Domain Issues

From: Jasper Smith (jasper_smith9_at_hotmail.com)
Date: 05/02/05 

Date: Mon, 2 May 2005 20:15:36 +0100

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/default.aspx?scid=kb;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@discussions.microsoft.com> wrote in message 
news:6CF3EF95-5BC9-426C-A4CD-41DF8DF24506@microsoft.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

Relevant Pages

  • Re: SQL 2000 SP3 and NT4 Domain Issues
    ... > to set the job owner to sa. ... > Jasper Smith (SQL Server MVP) ... > "Mike Mattix" wrote in message ... >> the second time I just stopped and restarted SQL Server (I was remote the ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2000 SP3 and NT4 Domain Issues
    ... Jasper Smith (SQL Server MVP) ... "Mike Mattix" wrote in message ... >> to set the job owner to sa. ... >>> the second time I just stopped and restarted SQL Server (I was remote ...
    (microsoft.public.sqlserver.security)
  • Re: Backing up transaction logs
    ... DB Maintenance Plan 'DB Maintenance Plan1'' ... I tend to set job owner to sa to ... >Jasper Smith (SQL Server MVP) ... >> base as well as the transaction log. ...
    (microsoft.public.sqlserver.security)
  • Re: SQLAgent error with job : The owner (domainSQLServerAdministratorUser) of job Optimizations Job
    ... The workaround is as you have found, to set the job owner to sa. ... Jasper Smith (SQL Server MVP) ... domain-controlers W2003 with AD. ...
    (microsoft.public.sqlserver.security)
  • Re: Testing Query Performance - clear out cache
    ... it runs the first time, it runs really fast the second time. ... plan cache, and DBCC DROP CLEANBUFFERS to clean the data cache. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)