OS: Windows 2000 Server
HM: 5.82 Beta (tested with 5.66 as well)
Test Method: NT Event Log
Problem: it doesn't work at all. It doesn't detect the failed event we're monitoring. Tested now with two different servers in different domains with different hardware and OS (Server and Advanced Server).
This problem was already reported by mail but never solved.
Evet Viewer check not working
Thank you, I found our conversation in mail archives. As you remember we cannot reproduce this problem, we have tested HostMonitor using your log file - it works fine. And we have not find any mistake in our code, what else we can do? 
BTW: We have not received reply to our last mail (December 01, 2005)
Regards
Alex
BTW: We have not received reply to our last mail (December 01, 2005)
Regards
Alex
As I remember we have used your test settings for testing, and it works. So problem is caused not by event log record and not by test settings.. may be something wrong with your system? Can you install HostMonitor on different system?Anyway, can you provide me with an example of a working test.
Regards
Alex
Well, installed in another computer with the same setup (SP/Patches) but different hardware. In this computer it works. 
Now I have no clue why it doesn't work in the other. Can you tell me what the code does so I can think of any particularity that might render the test to report always valid. :/
EDIT: well, I did two changes that seem to change the setup, I didn't set a computer (Any instead of the computer name) and I used the report about all "bad" events. What can I expect from these two changes? Any problem?
Now I have no clue why it doesn't work in the other. Can you tell me what the code does so I can think of any particularity that might render the test to report always valid. :/
EDIT: well, I did two changes that seem to change the setup, I didn't set a computer (Any instead of the computer name) and I used the report about all "bad" events. What can I expect from these two changes? Any problem?
http://www.ks-soft.net/hostmon.eng/mfra ... m#chkNTLogEDIT: well, I did two changes that seem to change the setup, I didn't set a computer (Any instead of the computer name) and I used the report about all "bad" events. What can I expect from these two changes? Any problem?
If you set "Any" in "Computer" filter, event recorded from any computer can be considered as "Bad".
If HostMonitor finds the event when you specify "any" but HM does not "see" the event when you have typed specific name, may be you misspelt the name?
Could you try to make the same changes on 1st system, where HostMonitor was installed before?
Quote from the manual:and I used the report about all "bad" events. What can I expect from these two changes?
Report about all "Bad" events
In opposite to previous mode, with this option enabled HostMonitor will inform you about each event that satisfies specified requirements. This option is useful when you use one test item to check for different error events (e.g. you are checking for any event with "Failure Audit" type). BTW do not forget to use "Repeat: until status changes" option for appropriate alert actions.
Regards
Alex
I didn't misspell the name for the DAEMON test as it didn't use that option, but could be possible with the other check I have as it is over a cluster and it has 4 different names (node, database, IIS).
Anyway, that test was updated as detailed before and still doesn't report when a warning is shown.
Where is that "Repeat: until status changes" option? I can't find it in any part of the test configuration window.
Anyway, that test was updated as detailed before and still doesn't report when a warning is shown.
Code: Select all
;-----------------------------------------------------------------------------
;- HostMonitor`s export/import file -
;- Generated by HostMonitor at 21/02/2006 10:14:27 -
;- Source file: C:\Program Files\HostMonitor4\HMList.hml -
;- Generation mode: Selected_Tests -
;-----------------------------------------------------------------------------
; ------- Test #01 -------
Method = NTLog
;--- Common properties ---
;DestFolder = Root\Servidores\Peru\DATACOD\
Title = DATACOD: smppGw events
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 300
Alerts = Send Mail smppGw
ReverseAlert= No
UnknownIsBad= No
UseCommonLog= Yes
PrivLogMode = Default
CommLogMode = Default
SyncCounters= Yes
SyncAlerts = No
DependsOn = list
MasterTest-Alive = DATACOD: smppGw
;--- Test specific properties ---
Computer = \\DATACOD
Log = Application
Source = smppGw
Username = EWAY\administrator
Password = ********
CheckComp = Any
CheckType = AnyFromList
CheckID = AnyFromList
CheckDescr = Any
CompList =
TypeList = Warning
IDList = ^M4100^M4099^M4097^M
DescrList =
ReportMode = AllEvents
;-----------------------------------------------------------------------------
; Exported 1 testsSo, what do we have? HostMonitor works fine everywhere except one of your systems. Something does not work correctly on that system but its hard to investigate what exactly.
My suggestion - keep HostMonitor on system that works fine.
Usually people use "Report about all events" test option together with " Repeat: until status changes" alert option. But its up to you, it depends on what exactly do you need.
Regards
Alex
My suggestion - keep HostMonitor on system that works fine.
This this "action" option.Where is that "Repeat: until status changes" option? I can't find it in any part of the test configuration window.
Usually people use "Report about all events" test option together with " Repeat: until status changes" alert option. But its up to you, it depends on what exactly do you need.
Regards
Alex
I think you misunderstood.
I checked with the DAEMON test it was reported first. That now works in the old installation of Host Monitor as well.
The test that fails (the one of the check over a cluster, that one I posted last), is doing so in BOTH systems. So, no it's not a solution to change installation as it doesn't work in a new one as well.
I checked with the DAEMON test it was reported first. That now works in the old installation of Host Monitor as well.
The test that fails (the one of the check over a cluster, that one I posted last), is doing so in BOTH systems. So, no it's not a solution to change installation as it doesn't work in a new one as well.