[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


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

Posted on 2010-01-06
Medium Priority
Last Modified: 2012-05-08
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.
Question by:Dinesh Subramanian
  • 2
  • 2

Assisted Solution

liorfr earned 2000 total points
ID: 26198205
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.

Author Comment

by:Dinesh Subramanian
ID: 26198818
What is Dr. Watson?, and i have checked with application, their are only viewstate errors occurring in the application, not unhandled exceptions

Assisted Solution

liorfr earned 2000 total points
ID: 26199099
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.

Accepted Solution

Dinesh Subramanian earned 0 total points
ID: 26245423
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.

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
By, Vadim Tkachenko. In this article we’ll look at ClickHouse on its one year anniversary.
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Suggested Courses
Course of the Month20 days, 2 hours left to enroll

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question