February 2, 2006 at 9:59 am
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
February 20, 2006 at 9:45 am
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
March 20, 2006 at 4:52 am
I have the same problem.
Can I just ignore this for now?
Thanks,
Ian
March 20, 2006 at 5:22 am
May 15, 2006 at 10:32 am
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"?
July 19, 2006 at 11:30 am
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 🙂
August 29, 2006 at 12:10 pm
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.
January 22, 2007 at 11:20 am
env: "Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Apr 14 2006 01:11:53 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1) "
We are still seeing the SQL Agent log flooding after SP1.
March 5, 2007 at 12:14 pm
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?
April 16, 2007 at 8:42 pm
Any update on this yet? I have sql2005 running win2003/sp1 on a x64 cluster. we are getting the same message...
April 17, 2007 at 6:53 am
I've not seen this error since I went from RTM to SP2
April 17, 2007 at 1:48 pm
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
April 18, 2007 at 11:18 am
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.
August 17, 2012 at 1:27 am
I am getting this error on SQL 2005 SP2 32 bit after configuring logshipping.
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply