Unable to read local eventlog (reason: 1130).

[slipfrase]

Guys/Gals,

I am wondering if anyone has come across this error in the application event log?

We are running, a dual 1ghz p3 server with 1gb of ram, and on Saturday morning, it crashed with low virtual memory erorrs and had to be restarted.

In the event log, there are loads of the these erorrs:

Event Type: Error
Event Source: SQLServerAgent
Event Category: Alert Engine
Event ID: 318
Date: 21/02/04
Time: 03:15:16
User: N/A
Computer: GHLPNT01
Description:
Unable to read local eventlog (reason: 1130).

I fixed the problem by dialing in, and rebooting the server, but whats weird is that no one was in using it. I am worried that it might happen during the day when the server is under heavy load.

Any ideas, suggestions would be greatly appreciated.

 

[RobertT687]

Which version of SQLServer are you running?
Which OS?
Are you manually setting the amount of virtual memory for SQLServer or allowing SQLServer to dynamically adjust it?
How about the OS? Are you allowing it to dynamically adjust virtual memory or manually setting it?
How much free disk space do you have on the boot drive or on the drives specified for paging?
Also what other apps are running on the server?
It may not have been SQLServer that caused the crash.
As for the message --Unable to read local eventlog (reason: 1130)--
I've seen this before when I manually clear the event log or, as in your case, when there is an uncontrolled shutdown (crash).

 

[slipfrase]

Hi Robert,

Thanks for you quick reply,

SQL server 2000 standard (SP3a)
Windows NT SP6

Memory settings in SQL server are set to dynamic, couldn't see any settings for virtual memory in SQL server enterprise manager.

Virtual memory is set to 750mb (Which I have just noticed, from experience, this should usually be set to 2.5 times size of main memory), only have 750mb of free disk space on c drive, and 1gb partition for page file.

Do you think this is my problem?

Touchpaper Helpdesk software, and intel landesk computer management are running on the server.

 

[RobertT687]

All the SQL server setting look reasonable to me.
We run a datawarehouse with less memory (512mb) and tons of users and that server has never crashed for memory issues.
750mb should be enough free space on C:\.
I think the culprit has to be one of the other apps running on the server.
If the entries are still there, look thru the Event viewer for messages around the time of the crash coming from other apps. There may be something there to shed more light on the crash.

Good Luck!

 

[slipfrase]

I think the culprite is the virtual memory being set to only 750mb on the server, as from what I have read sql server grabs as much main memory as possible, so it doesn't need to wait from other applications releasing the memory if it needs it. This meaning that the page file would almost certainly be full, and looking at the commit charge it is maxed out. Got a change control to create a new page file on a different drive tonight for 2.5gb, which should hopfully put my mind at ease.

Thanks for all your help Robert, it is much appreciated.

Fraser

 

[SQLBill]

Check your most recent SQL Error logs and see if they give any insight...they can be found at:

Program Files/Microsoft SQL Server/Instance_name/log/ERRORLOG.

Right click on the file and open with NotePad.

-SQLBill