Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SQL Agent Error Flood Expand / Collapse
Author
Message
Posted Thursday, February 2, 2006 9:59 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, June 3, 2013 9:53 PM
Points: 433, Visits: 619

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




Post #255353
Posted Monday, February 6, 2006 8:00 AM
SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, May 18, 2007 3:36 PM
Points: 10,039, Visits: 1
No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!
Post #255997
Posted Monday, February 20, 2006 9:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 28, 2010 2:11 PM
Points: 1, Visits: 9
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
Post #259935
Posted Monday, March 20, 2006 4:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, November 23, 2014 10:13 PM
Points: 1, Visits: 29

I have the same problem.

Can I just ignore this for now?

Thanks,

Ian

Post #266866
Posted Monday, March 20, 2006 5:22 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, September 26, 2007 7:16 AM
Points: 50, Visits: 2
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

Post #266875
Posted Monday, May 15, 2006 10:32 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, March 20, 2014 2:17 PM
Points: 14, Visits: 43
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"?
Post #280077
Posted Wednesday, July 19, 2006 11:30 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, November 13, 2014 12:11 PM
Points: 331, Visits: 558
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


Post #295597
Posted Tuesday, August 29, 2006 12:10 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:10 PM
Points: 192, Visits: 135

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.




Post #304753
Posted Monday, January 22, 2007 11:20 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, February 21, 2007 4:08 PM
Points: 32, Visits: 1

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.

Post #338745
Posted Monday, March 5, 2007 12:14 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, October 21, 2011 12:17 PM
Points: 103, Visits: 158
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?
Post #349223
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse