sqlagent.out

[dba999]

Hello,

I have the following error message in the sqlagent.out file, looping
each minute.

2005-12-19 10:58:54 - ! [298] SQLServer Error: 14262, The specified
@job_id ('254D5C3B-CB1F-4B02-AD79-FF5AFE343E3B') does not exist.
[SQLSTATE 42000] (ConnExecuteCachableOp)

I restarted the sqlagent and ms-sqlserver service, but did not fix the
problem.

Thanks

Diane Lavoie

[Razvan Socol]

Hi, Diane

Try the following:

USE msdb
SELECT plan_name FROM sysdbmaintplans p
INNER JOIN sysdbmaintplan_jobs pj ON p.plan_id=pj.plan_id
WHERE job_id NOT IN (SELECT job_id FROM sysjobs)

If you get any result from this query, delete and recreate the
specified DB Maintenance Plans.

Razvan

[Diane Lavoie]

Hi Razvan,

thanks for your reply, but the query does not return any row. I scanned
almost all tables in to found that jobid number but did found anything.

Each 20 seconds, there is an entry in the sqlagent.out and the
eventviewer windows log concerning this non-existent job.

Do you know anything about that 'ConnExecuteCachableOp'. Seems it is the
exe looking for the job.

Diane
*** Sent via Developersdex http://www.developersdex.com ***

[Razvan Socol]

Hi, Diane

Use Profiler to identify the statement and the program that calls this
job. If you do this on a production server, use some filters to see
only the relevant events (for example, database='msdb' and maybe
hostname='yourserver').

Razvan

[Diane Lavoie]

Hi Razvan,

I did the trace in the profiler and got the following:

EXECUTE msdb.dbo.sp_delete_job @job_id =
0x3B5C4D251FCB024BAD79FF5AFE343E3B
This job is executed each 10 seconds with the pid 72 which is the
sqlagent pid. This job does not exist in msdb.

Do I kill the pid 72 or maybe I should insert this job in the sysjobs
table of msdb......

Thanks
Diane
*** Sent via Developersdex http://www.developersdex.com ***

[Razvan Socol]

Hi, Diane

Try executing the following:

DECLARE @job_id uniqueidentifier
EXEC sp_add_job @job_name='test', @job_id=@job_id OUTPUT
UPDATE sysjobs SET job_id=0x3B5C4D251FCB024BAD79FF5AFE343E3B
WHERE job_id=@job_id
EXEC sp_delete_job @job_id=0x3B5C4D251FCB024BAD79FF5AFE343E3B

If it is still executed, did set up log shipping sometime ? Or
transactional replication ? Do you have other servers (that may be
executing a job on this server) ?

Razvan