August 20, 2008 at 4:37 am
SQL Server 2000 Developer Edition.
Anyone seen this problem before?
I am currently administering a server built by someone else that runs SQL Server Agent jobs successfully, but does not update the job history.
The max job history is set high enough.
I traced the jobs using SQL Profiler and the SQL Server Agent logging. Everything runs OK until the job history should be updated. Error 14262 is seen in the SQL Server Agent log saying the job id does not exist. But I dumped the job cache and the job id DOES exist!
If SQL Server Agent could not find the job at all I can understand. But to find it, run it, then not find it - weird. It is beginning to sound like server rebuild time...
The SQL Server Agent trace looks like this (zapped out the server name of course):
[177] Job test2 has been requested to run by User xxxxxxxx\sqladmin
[297] SQLServer Message: 14262, The specified Job ('0375AF51-2DA7-4A7A-94DF-0E6D31BA7B74') does not exist. [SQLSTATE 01000] (ConnExecuteCachableOp)
[184] Job completion for test2 is being logged to sysjobhistory
[297] SQLServer Message: 14262, The specified Job ('0375AF51-2DA7-4A7A-94DF-0E6D31BA7B74') does not exist. [SQLSTATE 01000] (ConnExecuteCachableOp)
Regards.
January 5, 2010 at 8:55 am
I've seen this when the SQL Agent account doesnt have rights to the database server. If you have removed Builtin\administrators and the agent runs as local system, add the login "NT AUTHORITY\SYSTEM" with sysadmin privs.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply