SQL Server Scheduled Job - Status: Failed - Unable to determine ...

Question

SQL Server Scheduled Job - Status: Failed - Unable to determine ...

Brandon_Green

SSC Eights!

Points: 948
More actions
April 12, 2004 at 12:04 pm

#163538

So the SQL 2000 server runs SQL authentication...Any ideas? I have tried changing the agent user account but can't seem to get them to like each other.
Brandon
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date:  4/12/2004
Time:  10:54:42 AM
User:  N/A
Computer: ERP
Description:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1'' (0xA4F2B04CB9F8DF488C9516F40724A9CF) - Status: Failed - Invoked on: 2004-04-12 10:54:42 - Message: The job failed. Unable to determine if the owner (DOMAIN\Administrator) of job DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\Administrator'. [SQLSTATE 42000] (Error 8198)).
"Change the job owner to a standard SQL Server user or system administrator (sa)."

The domain admin group was a member of the local admins, but went ahead and added the "administrator" account specifically just in case....

Upgrade to Microsoft Windows 2000 and add the Pre-Windows 2000 Compatible Access Group. Next, add the Everyone group to the Pre-Windows 2000 Compatible Access Group.

We are running 2003, and these account already exist in the pre-windows 2000 comp group.

GivThx SSCommitted Points: 1758 More actions · Answer 1

If ur job is for backing up DB or any kind jobs to other server not in the same server, U need to run ur SQL agent with network user that has a permission to access to that server. If u run ur agent with local system account, ur job can not get out of from ur server because local account is for only local.. If this senario fits to u, U need to create network ID that has a permission to other server as well as local server. I nomally put this ID to local adminitrator group for eack server but not network administrator group.

Hope this will help..

Thx

Jay

Brandon_Green SSC Eights! Points: 948 More actions · Answer 2

I am using the domain administrator account for the SQL agent startup as indicated on services...

I have also verified that the administrator account has the owner role given to it under the roles section of this particular database in Enterprise Management Console...

This user account has full rights to the \\backupserver\share\path that I wish to back up the files to.

I recieved this error when manually ran the optimization portion of the job trying to rule out a network user permission problem.

Event Type: Warning

Event Source: SQLSERVERAGENT

Event Category: Job Engine

Event ID: 208

Date: 4/12/2004

Time: 11:45:14 AM

User: N/A

Computer: ERP

Description:

SQL Server Scheduled Job 'Optimizations Job for DB Maintenance Plan 'DB Maintenance Plan1'' (0x50D92115DB2AD34AAE34FD925688A115) - Status: Failed - Invoked on: 2004-04-12 11:45:14 - Message: The job failed. Unable to determine if the owner (DOMAIN\Administrator) of job Optimizations Job for DB Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\Administrator'. [SQLSTATE 42000] (Error 8198)).

Brandon_Green SSC Eights! Points: 948 More actions · Answer 3

Here is what the SQL log is saying...

2004-04-12 12:02:25 - ! [298] SQLServer Error: 8198, Could not obtain information about Windows NT group/user 'DOMAIN\Administrator'. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

GivThx SSCommitted Points: 1758 More actions · Answer 4

Hi, Brandon

I am not sure u can backup into UNC path by schedule. YES, u can backup into network when u manually back up the DB but not by schedule.. As far as I know.. and I tried but I did not work because SQL server did not recognize network mapping drive as well as UNC path.. Probably I am wrong.. I need other DBA's opinion for this..

And instead putting ID into role, try put ID into local Admin group and try it.. See that works

AS u know, SQL agent needs to have a permission to run local service as well as other services. If u just put that into role, I am not sure that will cover all of permissions. However if u put ID into local admin group, u dont need to worry about. After that runs, u can find what servvies are needed for Agent by eliminating permission..

Thx

Jay

cpyne Mr or Mrs. 500 Points: 512 More actions · Answer 5

We had this same problem. The easiest fix is to make the job be owned by SA. Here's the article that lists the other fix:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q241643.

Brandon_Green SSC Eights! Points: 948 More actions · Answer 6

Rheejay:

I wasn't to sure about he UNC or mapping, but I thought this worked before we move rebuilt the backup target...but I am not for sure on this.

What do you mean by putting "ID" into local admin group...

-----------------------------------------------------------------------------

Cpyne:

Brandon_Green SSC Eights! Points: 948 More actions · Answer 7

Could the MSSQLSERVER service running as LocalSystem and the SQLSERVERAGENT running as domain\administrator be causing this problem?

cpyne Mr or Mrs. 500 Points: 512 More actions · Answer 8

I'm not sure about the pre windows 2000 compatability fix. We fixed it by changing the job ower to SA.

Double click the job that is failing in Enterprise Manager. Set the "owner" box to SA and try running it

cp

Brandon_Green SSC Eights! Points: 948 More actions · Answer 9

Setting the owner to SA solved the problem. Thanks for all of the help with this.

Alamir SSCertifiable Points: 6085 More actions · Answer 10

by the way, i also had the same job failure, but the job was working correctly before this

the problem that i discover that the server lost the comunication with out Domain Controller (which has Active Directoy on it) in this momenet .. so the user authontication on DC server is not found ... so the job failed

I hope this help other poeple

Alamir Mohamed
Alamir_mohamed@yahoo.com