September 15, 2009 at 3:56 am
On 3 occasions recently SQL server agent has been unable to start jobs. The following error message is written to the system event log:
'Timeout 30000 milliseconds) waiting for a transaction response from the SQL agent$
EventID is 7011 and Source is Service Control Manager.
I noted this morning that the SQL Server agent had used a huge amount of cpu - 4 times that of SQL server. The only way to fix this was to restart the SQL server agent service via the SQL Server service manager.
The server has 4 cpu (dual core) with 4GB of ram, Windows 2003 SP2 and SQL Server 2000 SP4 and uses a named instance. The databases reside on SAN disks.
Has anyone experienced anything similar?
October 5, 2009 at 8:22 am
We have resolved the problems as follows although this doesnt address why the problem occurred in the first place:
We used MOm to monitor the increase in cpu usage by the SQL server agent over 5 minute intervals and noted that the increase started regularly at about 12:30 and would disappear at midnight. We have two jobs which are started just after midnight and run all day to monitor for updated jobs and database objects. Changing these jobs to run for 2 12 hour periods per day fixed the problem.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply