I have a number of different tests which are performed against a server. The DNS service test works, the Login service test works, the UNC directory test works, but an Event log test returns "unknown."
It does this regardless of who I "connect as." Configuring the test (selecting an Event log, selecting an Event ID, etc.) all suggest that HM is talking to the server...
Any suggestions would be appreciated.
Event Log test "unknown"
-
- Posts: 23
- Joined: Sun Oct 26, 2003 6:58 pm
That's odd...when I first created this test, I didn't get this error at all. In fact, it did a little pause before it showed the drop down list which made me think it was really connecting to the other server before showing the drop list of logs or Event sources.
But now when I drop down either of those list boxes, I get the error:
Nick
But now when I drop down either of those list boxes, I get the error:
Thanks.Cannot retrieve list of Event Log sources from \\servername (System).
Will be used local system list
Nick
Nick,
What about my questions? Version of HostMonitor and how it performs this test (by itself or using RMA)?
Regards
Alex
If HostMonitor did not show error, it means there was no error. Something changed. Probably you changed account that is used by HostMonitor? HostMonitor needs power user account to perform NT Event Log test but it needs admin account to retrieve list of log sources. Also it needs to have access to remote registry, probably "Remote Registry" service stopped on that server?That's odd...when I first created this test, I didn't get this error at all. In fact, it did a little pause before it showed the drop down list which made me think it was really connecting to the other server before showing the drop list of logs or Event sources.
What about my questions? Version of HostMonitor and how it performs this test (by itself or using RMA)?
Regards
Alex
-
- Posts: 23
- Joined: Sun Oct 26, 2003 6:58 pm
Oops...version 4, not RMA.
Hmmm...I tend to keep trying different things until it works, so I probably did try admin and then also other accounts with less access.
Will need to verify but yes, remote registry is probably stopped.
So it sounds like Admin rights and remote reg should do the trick.
Cheers.
Nick
Hmmm...I tend to keep trying different things until it works, so I probably did try admin and then also other accounts with less access.
Will need to verify but yes, remote registry is probably stopped.
So it sounds like Admin rights and remote reg should do the trick.
Cheers.
Nick