MONITOR.EXE & DATALOG.EXE Alerts Have Invalid System Log DataLast reviewed: September 5, 1995Article ID: Q136148 |
The information in this article applies to:
SYMPTOMSThe system log displays an alert with the source DATALOG, but misses data for, or displays random characters for, the Value and Trigger fields. This problem occurs, when you run MONITOR.EXE along with DATALOG.EXE (Data Logging Service) to report an alert in the system log based on the LogicalDisk and %FreeSpace parameters, if hard disk space runs low. The Value field should display the amount of current free disk space that triggers the alert, and the Trigger field should display the percentage value of low, free disk space that you specify to cause the alert. NOTE: MONITOR.EXE is a command line utility ships with the Windows NT 3.5 Resource Kit. MONITOR.EXE controls the Data Logging Service that performs the same function as the Alert and Logging facility in Performance Monitor. You can schedule the DATALOG.EXE file to start automatically using MONITOR.EXE and the AT.EXE command, but Performance Monitor must be started manually.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 3.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
WORKAROUNDTo work around this problem, use Performance Monitor instead of MONITOR.EXE and DATALOG.EXE. For example: Assume you have a C drive with 150 MB total space. To be alerted every five minutes if there is less than 50% disk space free on your C drive:
|
KBCategory: kbtool kbbug3.50
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |