September 2, 2016 at 8:27 pm
I have server where I had notifications set up to go to an operator. I decided to go with another means of reporting job failures, so I removed all notifications from the jobs and deleted the operator. Afterwards my agent error log is filling up with "Message
[298] SQLServer Error: 14262, The specified @operator_name ('SQL Job Failure') does not exist. [SQLSTATE 42000] (ConnExecuteCachableOp)." I have verified that no job has an operator_id of any kind in it and the operator 'SQL Job Failure' truly does not exists. I have failures being emailed to me as well, so not only are they going into the error log, they are filling up my inbox. This is driving my bonkers as I have now spent close to two hours trying to figure it out. Please, does anyone have any ideas?
September 4, 2016 at 11:02 am
If you have already checked sysjobs and sysoperators, have you checked maintenance plans and alerts? Any chance you have a job step that is executing:
sp_notify_operator @name = 'SQL Job Failure'
You could query the command column in sysjobsteps to search for that command or even SQL Job Failure.
Sue
September 5, 2016 at 1:25 pm
I still never found a reference to that operator, but did have some alerts set up for replication. I deleted them and it seems to have solved the problem. Very odd, but thanks for pointing me in that direction.
September 5, 2016 at 2:07 pm
That is weird but there isn't much for referential integrity in msdb so I'm not surprised.
Glad it's working though - thanks for posting back!
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply