We have SQL SERVER 2005 RTM
We have 10-15 jobs, some of them are called from store procedures, some are scheduled and some of them are running for hours.
suddenly i found out that some jobs are running for 2 days and they have status Executing: 0 (unknown) . When i try to stop them i get error messages:
Stop failed for Job
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Unable to post notification to SQLServerAgent (reason: The maximum number of pending SQLServerAgent notifications has been exceeded. The notification will be ignored.) (.Net SqlClient Data Provider)
Error Number: 22022
I don't see any locks, deadlocks or any other performance issue.
I went to error log file viewer and found out there was lot of warnings like:
 Request to run job xyz (from User xyz) refused because the job already has a pending request from User xyz
We are going to restart SQL SERVER Agent service, but does anybody know what could be the reason for this? any ideas?
If you don't like how things are, change it! You're not a tree.