Microsoft KB Archive/883551

= You may receive the &quot;Error 8198 the job failed” error message on a computer that is running SQL Server Agent jobs that are installed by BizTalk Server 2004 =

Article ID: 883551

Article Last Modified on 10/28/2004

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Partner Edition
 * Microsoft BizTalk Server 2004 Standard Edition

-





SYMPTOMS
When one or more of the SQL Server Agent jobs that are installed by Microsoft BizTalk Server 2004 fail, you receive an error message that is similar to the following error message:

The job failed. Unable to determine if the owner (domain\username) of job  has server access (reason: Could not obtain information about Windows NT group/user 'domain\username'. [SQLSTATE 42000] (Error 8198)).



CAUSE
This problem may occur when the job is owned by a Microsoft Windows 2000 authenticated user or by a Microsoft Windows Server 2003 authenticated user. Also, the problem occurs when the job is run from the one of the following:
 * A local Windows 2000 administrator or a local Windows Server 2003 administrator
 * A schedule, after being scheduled



RESOLUTION
To resolve this problem, change the job owner to a standard SQL Server user or to a standard SQL Server system administrator. To do this, follow these steps:
 * 1) Start SQL Server Enterprise Manager.
 * 2) Expand Microsoft SQL Servers, and then expand SQL Server Group.
 * 3) Expand your server name.
 * 4) Expand Management, and then expand SQL Server Agent.
 * 5) Click Jobs. In the right pane, right-click the job that failed, and then click Properties.
 * 6) In the Properties dialog box, click Owner on the General tab to display the list of owners.
 * 7) In the Owner list, click the SQL Server user who you want to use. Alternatively, click sa, and then click OK.
 * 8) When you are prompted to stop and to restart SQLAgent, click OK.
 * 9) Restart any instances of SQL Server.

Note We recommend that you also restart any other instances of SQL Server Agent that are installed on your server.

