MonitorWare Knowledge Base

Thanks in advance for all the help.

I have a currently running winsyslog server. This server and online web viewer have worked flawlessly for more than a year. So now they want to move the db from MSSQL to MYSQL.

The tables are created, and are being populated by events, however when I try to view the events from the web interface i get...

Microsoft OLE DB Provider for ODBC Drivers error '80040e21'

ODBC driver does not support the requested properties.

/EventsOnline.asp, line 353


Line 353 is:

352 <% 'Opening Recordset
353 rs.Open sql_cmd, oConn, 1, 2
354 %>

any ideas? The ODBC connector should be fine since the database populates with data.

The ConfigSettings.asp file looks like:

<% dtToday = now() %>
<% ' This page contains all configurable settings
' for the online syslog viewer.
'
' Make changes HERE - and nowhere else!
'
' This is part of the WinSyslog product.
' See http://www.winsyslog.com for support & updates
'
' Copyright (C) 2001 Adiscon GmbH (http://www.adiscon.com)

' °°°°°°°°°°°°°°°°°°°° CONFIG SETTINGS - CHANGE FROM HERE °°°°°°°°°°°°°°°°°°°°

' *** Page to appear first ***
' True : Shows the Selection Page first
' False : Skips the selection Page and begins immediatelly
cfgShowSelectionPage = "false"

' *** Name of ODBC DSN ***
strConfODBCDSN = "tink-syslog"
' *** Userid of ODBC ***
strODBCUserid = "root"
' *** Password of ODBC ***
strODBCPwd = ""

' *** Display Events from (Predefined)***
' (This is also the default selection if the Selection Page is skipped)
' Valid Values for cfgPredefinedDate :
' today,
' last 2 days, last 3 days, last 4 days,last 5 days, last 6 days,
' last 1 week, last 2 weeks, last 3 weeks,
' last 1 month, last 2 months, last 3 months, last 4 months,
' this month, this year
cfgPredefinedDate = "today"

' *** Display Events Between (Manually)***
' Valid values for cfgdatebeginday, cfgdateendday : 1 - 31
' Valid values for cfgdatebeginmonth, cfgdateendmonth : 1 - 12
' Valid values for cfgdatebeginyear, cfgdateendyear : 2000 - 2012
' Additional valid values
' cfgdatebeginday, cfgdateendday : Day(dtToday) displays today's day
' cfgdatebeginmonth, cfgdateendmonth = Month(dtToday) displays today's month
' cfgdatebeginyear, cfgdateendyear = Year(dtToday) displays today's year
cfgdatebeginday = Day(dtToday)
cfgdatebeginmonth = Month(dtToday)
cfgdatebeginyear = Year(dtToday)
' *** and ***
cfgdateendday = Day(dtToday)
cfgdateendmonth = Month(dtToday)
cfgdateendyear = Year(dtToday)

' *** Order Events By ***
' Date : Date
' Facility : Facility
' Priority : Priority
' FacilityDate : Facility and Date
' PriorityDate : Priority and Date
cfgOrder = "Date"

' °°°°°° END CONFIG SETTINGS - DO NOT MAKE ANY CHANGES BELOW THIS POINT! °°°°°°
%>

Hello,

please update your ASPWebinterface. The latest version can you find at http://www.winsyslog.com/en/FAQ/How-can-I-view-syslog-messages-via-web.php

Please be sure that you set 'bUsingMysql = true' in your ConfigSettings.asp

I hope this solve the problem.

I replaced the original files in the web with the new ones and the error is the same.

I am using the MySQL ODBC driver version 3.51 and the database will populate with data but will not return results from the ASP interface.

Microsoft OLE DB Provider for ODBC Drivers error '80040e21'

ODBC driver does not support the requested properties.

/EventsOnline.asp, line 452

Line 452 is the same as in the previous error.

Hello,

we are currently working on this issue. Can you please try

Code: Select all

'Opening Recordset
rs.Open sql_cmd, oConn


instead of

Code: Select all

'Opening Recordset
rs.Open sql_cmd, oConn, 1, 2


Another customer had had the same problem. He got it solved by checking his database and tables names. Note, MySQL is case sensitive. Please be sure that the names are correct.

The Table name in the database was SystemEvents and the webs were asking for systemevents.

I dont know where the lowercase systemevents was taken from.

The database was originally imported from the included access DB to MSSQL and then exported with enterprise manager to MySQL.

The case sensitivity thing was the problem, thanks for the help!!

Fine