SQL Agent Error Flood

Question

SQL Agent Error Flood

Joe Clifford

SSCrazy Eights

Points: 8739
More actions
February 2, 2006 at 9:59 am

#113280

LOG] Unable to read local eventlog (reason: The parameter is incorrect)
I just had two seperate SQL Server 2005 Enterprise Edition machines suddently throw thousands of these errors within the last 24 hours. In both cases the the SQL agent and application event logs are just being flooded with a new entry every couple of seconds.
While the errors are being logged the Agent continues to run jobs (e.g. scheduled backups, etc.) without error.
A restart of the agent stops the errors and everything seems to be back to normal.
There is no commonality between the two machines, they are on different networks, domains, etc.
Both machines have been up >30 days and have not previously logged this error.
Anybody else seen this?
Thanks,
Joe
February 6, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply

Justin Cervero-303705 SSC Rookie Points: 41 More actions · Answer 1

According to some of the technet discussions, it is a known bug and has been fuxed in the SP1 Beta (not available to the public).

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124086&SiteID=1

Ian Smith-311835 Newbie Points: 3 More actions · Answer 2

I have the same problem.

Can I just ignore this for now?

Thanks,

Ian

IanR SSC Eights! Points: 938 More actions · Answer 3

I do as well. I'd love to see that service pack out soon.

New to the DBA world...thank you for your help!,

IanR

M Chapman SSC Veteran Points: 212 More actions · Answer 4

I am having the same error over here, win2k3 box w/ upgrade from ms sql 2000 to sql 2005. I then installed SP1 and it is still happening. Anyone have an idea? What parameter is the "incorrect parameter"?

Linda Johanning SSCertifiable Points: 6727 More actions · Answer 5

I just installed SQL 2005 service pack 1 on a test box and the errors went away. I'm going to install it on a production box soon--hopefully the errors will go away there too 🙂

David Lu SSC Eights! Points: 882 More actions · Answer 6

On our SQL2005 64bit, sp1 server, I just experienced the same error of "[LOG] Unable to read local eventlog (reason: The parameter is incorrect)" with every 5 seconds dumpping to the log.

After restart, it is gone. But it might come back, hope there is a sp2 to fix it.

Peter Daniels-376527 Valued Member Points: 60 More actions · Answer 7

We are still seeing the SQL Agent log flooding after SP1.

charles evans SSCommitted Points: 1865 More actions · Answer 8

I have this occurring on a Server Standard 2003 x64 box with Developers 64 bit SQL 2005 sp 1. I wonder if this is fixed in SP2?

aguo Grasshopper Points: 17 More actions · Answer 9

Any update on this yet? I have sql2005 running win2003/sp1 on a x64 cluster. we are getting the same message...

Anders Pedersen SSChampion Points: 11410 More actions · Answer 10

I've not seen this error since I went from RTM to SP2

williamminor SSCommitted Points: 1664 More actions · Answer 11

I have the same error (SQL Server 2005 SP1.) restarting the agent stops the error for a while but it always starts up again. Anyone find any solutions??

-WM

DBA

Mike Aarset Valued Member Points: 65 More actions · Answer 12

I just started getting these when I enabled Email alerts for Replication on some test servers.

If I figure this one out I will post something.

Ganeshkumar005 Ten Centuries Points: 1140 More actions · Answer 13

I am getting this error on SQL 2005 SP2 32 bit after configuring logshipping.