December 16, 2003 at 11:46 am
Hi,
I received the error:
SQLSERVERAGENT_Error: Unable to read local eventlog (reason: The data area passed to a system call is too small).
The database seems fine. I checked the SQL Server logs but there is no error.
Does anybody have any idea what this means or how to go about troubleshooting it ?
Thanks.
Albert P. Wun
Consultant - Data Management - DBC
CGI Services to BCE
595 Bay Street, Fl 11-00B, Toronto, ON, M5G 2C2
Albert P. Wun
Consultant - Data Management - DBC
CGI Services to BCE
Markham, Ontario, Canada
December 16, 2003 at 11:52 am
Can you provide more details what did you try to do? What service account do you use to run SQL Server Agent Service, Local system a/c, Domain User and their privilege in SQL Server?
December 16, 2003 at 2:31 pm
If possible run profiler and do the same you did when the Agent failed to know wich command could cause the error.
December 17, 2003 at 2:22 am
Is this something to do with the eventlog tidying itself (deleting old event etc) at the same time as sql agent is tring to write to it?
We see these errors occasionally too.
December 17, 2003 at 4:51 am
I see this error from time to time and have never been able to figure out what it meant.
October 6, 2004 at 12:54 am
Did anyone find out what this was about? We're getting the same error.
October 13, 2004 at 10:48 am
I received a similar msg in EventAppLog yesterday after a crash from an unrelated application. Microsoft Article 811484 explains it like this:
SYMPTOMS
When you set Dr. Watson as the default debugger, a SQLSERVERAGENT error with Event id: 318 may appear in Event Viewer immediately after an application generates an "unhandled exception" error.
For example, you might see messages similar to these in the Event Viewer Application log:
Source: SQLSERVERAGENT
Category: Alert Engine
Event ID: 318
Description: Unable to read local eventlog (reason: The data area passed to a system call is too small)
Source: DrWatson
Category: None
Event Id: 4097
Description: The application, C:\Program Files\<Application name> generated an application error. The error occurred on 12/21/2002 @ 00:21:09.282 The exception generated was c0000005 at address 10006045 (HTMLEdit)
CAUSE
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.
MORE INFORMATION
You can ignore the SQL Server Agent error Event id: 318. The error occurs because of another application failure that is running on the same computer where SQL Server is running. To prevent the error, troubleshoot and resolve the application error that is raised by the other application.
--------------------------------------------------------------------------------
March 23, 2005 at 7:13 am
In this case, sql is running on a remedy server and it is causing the logging into the database to time out. How can you fix this?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply