Re: SQL Agent Jobs Failing

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/01/05


Date: Tue, 1 Mar 2005 18:06:21 +0100

Is changing the job owner to "sa" an option? That will most probably solve the problem.

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"J.Jill" <JJill@discussions.microsoft.com> wrote in message 
news:59173D5F-9F15-49B8-95F2-42078CAC5437@microsoft.com...
>I have a number of job failing due to authentication issues.
> enviroment
> 2003 Standard Edition
> SQL 2000 Service Pack 3
> 2003 Active Directory Domain
> SQL Agent runs under a domain account with sysadmin rights
> Job owner is also a domain account with sysadmin rights
>
> The jobs run succesfully sometimes and fail other times.
> Error:
> Number 1 from Agent error log.
> [298] SQLServer Error: 8198, Could not obtain information about Windows NT
> group/user 'webad\mysqlagent'. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
>
> Number 2 from the job history log
> The job failed.  Unable to determine if the owner (WEBAD\myuser) of job
> myjobName has server access (reason: Could not obtain information about
> Windows NT group/user 'WEBAD\myuser'. [SQLSTATE 42000] (Error 8198)).
>
> Thank you..
> Bill
> 


Relevant Pages

  • Re: Trying to Move Group - SQL Instance Wont Start
    ... You can do a maintenance install and add the new nodes. ... You will have to undo the manual allowed nodes settings and then follow the instructions in "maintaining a failover cluster" for recovery from failure scenario 1. ... SQL 2000 on Windows Server 2003 allows up to four nodes in a cluster so you should be good to go. ... > Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Breaking a Sql Cluster
    ... If you are not going to have any extra SAN space, ... then remove the old instance and install a *clustered* SQL ... 2005 instance on that same cluster. ... SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Error -2147217900: failed to create SQL database
    ... We ran profiler to see what commands is the MSI passing to create the DB. ... SQL Server MVP ... database: ApplicationDb, ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Error -2147217900: failed to create SQL database
    ... SQL Server MVP ... we rebuilt the SQL cluster network today. ... database: ApplicationDb, ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Breaking a Sql Cluster
    ... "Tom Moreau" wrote: ... SQL Server MVP ... We have one local and one named instance of SQL 2000 on the cluster at ...
    (microsoft.public.sqlserver.clustering)