MonitorWare Knowledge Base

Gent's,

I'm getting the following error often. The asp page seems to work at times and will display pages of logs, but will generate this error randomly. Is this because the syslog daemon is trying to write to the database while I'm viewing it on the web? The database is a default MS Access 97 database that was converted to Access 2000.

HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

Technical Information (for support personnel)
Error Type:
Provider (0x80004005)
Unspecified error
/EventsOnline.asp, line 388
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Page:
GET /EventsOnline.asp
Time:
Sunday, July 20, 2003, 11:48:53 AM
More information:
Microsoft Support



The original eventonline.asp file is untouched, except I opened it once with Frontpage to view the code. Does this alter the ASP code in anyway?

confused wrote:The original eventonline.asp file is untouched, except I opened it once with Frontpage to view the code. Does this alter the ASP code in anyway?

Frontpage is sometimes dangerous - we know it alters HTML in ASP pages.

But I don't think it is the problem in this case. We sometimes see this issue when Microsoft Access is used as a backend. We are currently evaluating the cause, but were so far unable to to reproduce it in our lab.

If you intend to view larger amounts of log data, I would recommend moving on to either MSDE or MySQL. MS Access simply does not provide the performance you need for such. It is nice to get started, but the larger the data gets, the larger the problems get

Anyhow, I will keep you posted as soon as we have some more data an this issue.

I hope this at least clarifies a bit...

Rainer Gerhards
Adiscon

Hi. Let me join in this topic.

Then, could you show us the recommended system requirements and recommended configuration?

I often experience the similar ASP errors, with MSSQL. I have about 100 servers and 200 clients that send syslog data to the central server on Windows 2000 with Winsyslog and MSSQL Server 2000 (JPN) loaded.

Hardware:
128Mb Memory
600 Mhz Celeron
8GB HDD

OS: Windows 2000 JPN
Winsyslog version: 4.2
MSSQL Server 2000

When I confirm the event log of the machine I often notice the SQL Server produces error complaining that there is not enough resources and the database is locked...

I have composed several rules and admin tasks to delete unwanted and normal entries. Apparently the mem and the CPU is the issue, but I do not see how much of the memory should be added and how fast (in Mhz) the CPU has to be.

Hello,

Take a look at this. This will also help you out

http://www.winsyslog.com/Common/en/faq/ ... -error.php

Best Regards
Wajih-ur-Rehman
Adiscon