2003-08-26 MonitorWare Agent 1.3

Tuesday, August 26th, 2003

MonitorWare Agent 1.3

  • RFC 3195 Support(Client) – MonitorWare Agent now supports reliable syslog delivery via TCP when sending syslog messages. TCP syslog is implemented based on the new RFC 3195 and thus is standards-compliant.
  • RFC 3195 Support(Server) – The syslog listener service now also supports TCP syslog messages based on RFC3195. (more…)

Step by Step Guide for Viewing Syslog Messages on Web

Thursday, August 7th, 2003

Step by Step Guide for Viewing Syslog Messages on Web

Created 2003-08-07 by Wajih-ur-Rehman

Can you give me step by step guidelines for viewing Syslog Messages on Web?

Here is the step by step procedure for configuring Online Web interface for viewing Syslog Messages.

First, make sure that IIS is installed and running. Then follow these steps:

1. Download the zip file from one of the following links depending on your product version:

ZIP file for WinSyslog 4.x and MonitorWare Agent (10 KB) (If you have WinsSyslog 4.x or higher, MonitorWare Agent or EventReporter)

OR

ZIP file for WinSyslog 3.x (10 KB) (If you have WinSyslog 3.x)
2. Unzip the file. It includes some .asp files and a Help.html file. (In this Help file, all the details are given). Copy all of these files and put them in the folder "inetpub\wwwroot\YourFolder"

where YourFolder could be any name.

3. Now open the ConfigSettings.asp page. There you will find many variables. The most important ones that you would HAVE to set are the following:

' *** Name of ODBC ***
strODBCName = "NameOfMyDSN"

‘ *** Userid of ODBC ***
strODBCUserid = "sa"

‘ *** Password of ODBC ***
strODBCPwd = ""

Where NameOfMyDSN is the DSN name that points to your database. For Microsoft Access, you don’t have to specify any userid and password.

There are some other variables which you can set to filter events. Once you are done with this ConfigSettings, simply save this page.

4. Now open up the browser and write the URL. In the example that I am giving you it will look like this:

http://localhost/YourFolder/Default.asp

It will show you syslog messages from the database on the web (according to the filter conditions that you have set in the ConfigSettings.asp variables)

How to monitor a file on a remote machine?

Thursday, August 7th, 2003

How to monitor a file on a remote machine?

Created on 2003-08-07 by Michael Meckelein.

By default, MonitorWare Agent service uses the local system account. This account has no permission on remote machines. If you want to monitor a file on a remote system, the MonitorWare Agent service must log on as a user with administrator rights. This user must be exist on both system, local and remote. Also be sure, that the password is equal on all machines or – preferrably – use a domain account.

Here are the steps for monitoring a file on a remote machine:

  1. Add a File Monitor servicefilemonitor
  2. Use an UNC name for ‘File and path name’, e.g. \\remotemachine\share\filename.log
  3. Go to administrative tools -> Services
  4. Right click on AdisconMonitorWareAgent and select properties
  5. Select the ‘Log On’ tab and check Log on as: ‘This account’
  6. Enter a user with admin rights, this user must still exit on the remote machine!logontab

Logging to Different Files

Tuesday, August 5th, 2003

Logging to Different Files

Created 2003-08-05 by Wajih-ur-Rehman

How can I log the data from different devices to different files?

You can log the data of different devices in different files with just one click! Simply check "Include Source in file name" and restart the service. Different logfiles will be created and each filename will include the source of the message. It will now write the logs of different devices in different files.

Database Connection Problem

Tuesday, August 5th, 2003

Database Connection Problem

Created 2003-08-05 by Wajih-ur-Rehman

I am unable to Log the data to the database although I have provided the DSN to the software?

Please note that even if you have created the DSN with some login and password, you would still have to write that login and password in the Graphical User Interface of the Client program in proper text boxes because it creates the connection string using the name of the DSN, the login and the password.

Error opening language file

Tuesday, August 5th, 2003

Error opening language file

Created 2003-08-05 by Lutz Koch

When I start a MonitorWare Product, I get the following error:

"FATAL error opening the MonitorWare/WinSyslog/EventReporter/MoniLog language file. Please repair this using the Monitorware/WinSyslog/EventReporter/MoniLog Installer"

The reason for this error is that the language file got somehow deleted or renamed. This can occur with MonitorWare Agent, WinSyslog, EventReporter as well as MoniLog. To solve the problem, make sure the according language file is in your program directory.

You can download the files here: