Web interface problem

Support, Questions and Discussions on WinSyslog

Moderator: alorbach

Web interface problem

Postby javstech on Fri Jul 11, 2003 2:11 pm

I recently (re) installed winsyslog and everything is runng great, with the minor exception that in the web access inteface when i clink on the link to get details about the specific event, i get an unspecfied error from my server in details.asp. the browser displays:
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Error Type:
Provider (0x80004005)
Unspecified error
/winsyslogwebaccess/details.asp, line 61


Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)

Page:
GET /winsyslogwebaccess/details.asp

Time:
Friday, July 11, 2003, 9:08:05 AM


More information:
Microsoft Support

the IIS Logs are no more help, any ideas?
javstech
 

Postby alorbach on Fri Jul 11, 2003 2:19 pm

Hi,

this is the code line where the database connection is created.
Hrm, are you using MS Access as database?
And if, how big is the database?
Does the error happen all the time? Or just from time to time.
User avatar
alorbach
Site Admin
 
Posts: 867
Joined: Thu Feb 13, 2003 11:55 am

Postby javstech on Fri Jul 11, 2003 2:30 pm

i am using the template access DB right now, it has less than 100 entries in total at the moment, only have it monitoring one system until i get my rules and filters in place.

i can see the list of events from the database., but the details file is generating errors, if it is of any help all my permissions to the db are correct and it is running on windows xp
javstech
 

Postby javstech on Fri Jul 11, 2003 2:38 pm

i am also noticing that the eventonline.asp is getting an acess error on occassion, could i have something set up wrong with my odbc?
javstech
 

Postby alorbach on Fri Jul 11, 2003 3:14 pm

No ODBC is fine. This kind of error's are related to MS Access databases.

Let me say it in this way. MS Access databases are ok for testing, or distributing sample databases. They also work with ASP rather well.

However, if there is to much access on the Database (WinSyslog writes into it, a few ASP pages are opened at the same time), such problems / error's can occur.

At this position, it is usally a good Idea to switch over to MS SQL Server (or maybe MySQL).

You will find information regarding MS SQL Server in the WinSyslog manual (Hit F1 in the Client). For informations about MySQL, see the following article: http://www.winsyslog.com/en/FAQ/Setup-W ... -MySql.asp
User avatar
alorbach
Site Admin
 
Posts: 867
Joined: Thu Feb 13, 2003 11:55 am

Postby javstech on Mon Jul 14, 2003 1:37 pm

well, successfully switched to MySQL, had no success using winsyslog with the MyODBC 3.51 drivers(something funny between winsyslog and Myodbc) but it is working great with the 2.50 drivers, however, now i am getting errors at the same place at line 165:

Error Type:
ADODB.Recordset (0x800A0CC1)
Item cannot be found in the collection corresponding to the requested name or ordinal.
/winsyslogwebaccess/details.asp, line 165


any ideas?
javstech
 

Postby javstech on Mon Jul 14, 2003 2:21 pm

nevermind, found the problem- a typo on my part - now i feel stupid
javstech
 

Postby alorbach on Tue Jul 15, 2003 11:37 am

However, I am happy that the problem is solved ;)
Usually it are easy things like this (typos for example).
User avatar
alorbach
Site Admin
 
Posts: 867
Joined: Thu Feb 13, 2003 11:55 am

Google Ads



Return to WinSyslog

Who is online

Users browsing this forum: No registered users and 0 guests

cron