Error on startup (Error event ID: 7026) explained.

Created 2003-11-06 by Andre Lorbach.

Many Adiscon products (e.g. WinSyslog, EventReporter or MonitorWare Agent) are available in a 30 days trial version.
After this time, the Service will stop working and if you are not logged on interactive, you will not see an error message. However, an error message in the application eventlog is generated by the system. It looks like the following:

Event Type: Error 
Event Source: Service Control Manager 
Event Category: None 
Event ID: 7023 
Date: xx/x/xxxx
Time: x:xx:xx AM 
User: N/A 
Computer: MYCOMPUTER
Description: 
The service terminated with the following error: 
The system could not find the environment option that was entered.

The reason why you get this error is, because your trial is expired.
The Service will skip initialization and the system will catch this with the error above.
What to do if you purchased the software, entered the license name / key and you still get this error?

1. Check the license name, it has to spelled correctly and to be case sensitive. Otherwise the license will not work.
2. Contact support@adiscon.com for further assistance.

Trouble with a non-Adiscon product? Then see this description of event 7026!

Do you want to control your Windows Server/Workstation events and get alerted on errors?
Take a look at the EventReporter product website!

Analysis, monitoring, near-real-time alerting of the Windows event log can be done with EventReporter.

Take a Quick Tour to EventReporter to know more about its exciting features or directly download the free and full-featured 30 day trial version.

What is the difference between SETP and Syslog?

Created 2003-10-21 by Wajih-ur-Rehman

What is the difference between SETP and Syslog and what advantages does SETP offer over Syslog?

Following are some of the points related to traditional Syslog:

Its a UDP based protocol.
It doesn’t provide any guarantees of message delivery.
It doesn’t parses the data so most of the fields of MonitorWare Database would remain empty, if Syslog is used to send data to the database.
It is supported by EventReporter, WinSyslog and MonitorWare Agent.

For more details about Syslog, please visit:
http://www.monitorware.com/common/en/articles/syslog-described.asp

Following are some of the points related to SETP:

Its Adiscon’s proprietary protocol.
Its a TCP based protocol.
It provides guarantee of message delivery.
It parses the data out and hence all of the fields of MonitorWare Database would be filled.
It is supported by WinSyslog 5.0 Enterprise Edition and MonitorWare Agent (EventReporter 6.0 will also support SETP sending)
Since MonitorWare Console expects that all of the fields of the database have some values in it, it generates more meaningful reports with SETP as compared to Syslog (with which most of the fields are empty)

One thing to keep in mind is that if you are sending the data using SETP protocol, then on the receiving end there must be a SETP listener to receive that data. So, in no case it is possible that you send the data using MonitorWare Agent (which supports SETP sending) and receive that data using WinSyslog 4.x (which doesn’t support SETP receiving).

Please note that the syslog restrictions mentioned here apply to traditional, UDP based syslog. There are newer syslog standards available, most importantly RFC 3195. Adiscon is one of the yet few supporters of these new standards. With it, the reliability issues of syslog are solved. However, there are still length isuses, so that this is not the final solution. Adiscon is actively working with the standards bodies to improve syslog protocol’s capabilities. We hope that, in the medium to long term, we can provide the same benefits SETP offers over standardized syslog.

2003-08-29 MonitorWare Agent 1.3 released

MonitorWare Agent 1.3 Released

Adiscon today announced the immediate availability of MonitorWare Agent 1.3.
This version supports reliable syslog delivery via TCP. TCP syslog is implemented based on the
new RFC 3195 and thus is standards-compliant. Continue reading “2003-08-29 MonitorWare Agent 1.3 released”

Setup Error 1923

Created on 09-10-2003 by Lutz Koch.

I receive error 1923 when installing a MonitorWare Product like EventReporter, WinSyslog or MonitorWare Agent. What to do?

If you update one of those Products to a newer Version, you might get the following warning message:

Cause:
If you changed the Services properties (for example the Log On settings), the Installer will detect that the installed Service does not match that one from the Installation Package. So this Warning message is shown to inform you about this.

Resolution:
Just click the ignore button, the EventReporter, WinSyslog or MonitorWare Agent Service will be correctly updated, and custom changes in the Services properties will remain.

2003-08-26 MonitorWare Agent 1.3

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. Continue reading “2003-08-26 MonitorWare Agent 1.3”

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)

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?

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:

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

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

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

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: