March 14, 2006 at 3:26 am
Hi all,
Am getting the following error in the SQL Server Agent log whenever I try to start the SQL Server Agent:
"[LOG] Exception 5 caught at line 2981 of file ..\src\job.c. SQLServerAgent initiating self-termination"
Having had this land on my lap, it seems the problem could be related to the Decmeber release of critical updates - as this was when the problem arose. Does anyone know either:
a) what the error means; or
b) if anyone else got the error as a result of the december release of MS critical updates.
The server is a clustered Windows 2003 server (no sp1) setup with SQL Server 2000 SP4. As I said, all appeared to be working fine before the December 2005 release of MS updates.
I am currently looking into removing the MS update and the damage that may cause!
Thanks,
Dave.
March 15, 2006 at 2:58 am
Hi all,
Microsoft have found a way of getting around this problem. It seems that the processor counter (viewable thru the likes of perfmon) has been removed. How this has been removed, MS are unsure - it could be to do with the critical update mentioned in my first post.
Anyway, if anyone else gets this problem, you have go into the properties of the SQL Server Agent, click the 'Advanced' tab and then uncheck 'Idle CPU Condition' checkbox. If this is checked, the Agent makes uses the processor counter which is no longer available. The Agent then fails with the error mentioned in the first post.
Microsoft confirmed that this is a bug and, as yet, there is no fix for the problem. If the problem was caused by the critical update I will post another update.
Cheers,
Dave.
March 15, 2006 at 11:02 am
thanks for the feedback.
These kind the tiny brainteasers being solved make our day
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 16, 2006 at 9:07 am
Very welcome.
As a futher note (and I promise, the final one!):
Microsoft confirmed that the critical patch released in December 2005 did NOT cause the corruption/removal of the Processor performance counter. Microsoft did, however, off to give me an exe which would restore the base counters but they couldn't confirm if this would cause problems with the SQL counters that SQL Server itself installs. I declined to run the exe! But, should any of you ever lose some of your base Windows 2003 Server counters, you can ask MS for this exe - they will stress that it is relatively untested, use at your own risk, etc, etc.
Laters all.
Dave.
May 28, 2006 at 5:49 pm
Dave,
Just wanted to say you are a life saver!
This seems to be the only post about this problem any where!
Thanks again,
Wes
May 30, 2006 at 6:28 am
Hi Wes,
Glad the post was of use to you!
Cheers,
Dave.
May 30, 2007 at 9:17 am
+1 point to Dingle1975
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply