SQL Server 2000, Event Log Error, Error Id - 318

Unable to read local eventlog (reason: The data area passed to a system call is too small).

This error is recorded in the event log every minute in the production server, and because of this the SQL Server 2000 performance is very slow and the box is also working slow.

This indirectly affects my application and productivity.
Experts Please help me.
SQL-Error.JPG
LVL 2
Dinesh SubramanianSenior Software EngineerAsked:
Who is Participating?
 
Dinesh SubramanianConnect With a Mentor Senior Software EngineerAuthor Commented:
thanks bro;

I finally found that the viewstate error occurring in the web page was the cause for the SQL Agent 318 errors. and then now when i have solved those, the server is not getting this type of error,

finally, i commit the viewstate error in web pages cause this issue, by solving it, one could easily get rid of this error.
0
 
liorfrConnect With a Mentor Commented:
The SQLSERVERAGENT error Event id: 318 is a result of an unhandled exception raised by another
application that runs on the same computer as SQL Server. SQL Server Agent reads the
application event log to respond to SQL Server events defined in the SQL Server Agent alert.
Dr. Watson handles the "unhandled exception" and records the error information raised by
the application in the Windows Application log. SQL Server Agent reads the error entry
from the Windows application log and generates error Event id: 318.
0
 
Dinesh SubramanianSenior Software EngineerAuthor Commented:
What is Dr. Watson?, and i have checked with application, their are only viewstate errors occurring in the application, not unhandled exceptions
0
 
liorfrConnect With a Mentor Commented:
It is just a sample for an application that raises errors to the windows event log.
At any rate 318 is an error generated by SQL server agent which is caused by another application (which is not SQL server) writing error to the event log.
Are the viewstate errors the only errors in the event log?
If so, than they are the only ones responsible for the SQL agent 318 errors.
BTW - documentation states you can disregard the 318 errors and that they have no effect on SQL server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.