Alex,
It seems there is a problem with reading events on a 2003 server.
The description is not what I see with a eventvwr.
Sometimes the first line is ok, but the rest is rubbish ...
I can send you an eventlog if needed.
Regards,
Gert
Eventlog on Windows Server 2003
Hi,
I see it's not a problem of 2003. I had the same problem on 2000 systems too.
An example:
HM gives as description:
Message not found. Insertion strings:\Device\CPQCISSE0, Embedded Controller, 1, 5, 0
Eventvwr gives as description:
Logical Drive 1 of Embedded Controller has changed from status code 0 to status code 3.
Status Codes:
0 = OK
1 = FAILED
2 = NOT CONFIGURED
3 = INTERIM RECOVERY MODE
4 = READY FOR RECOVERY
5 = RECOVERING
6 = WRONG PHYSICAL DRIVE REPLACED
7 = PHYSICAL DRIVE NOT PROPERLY CONNECTED
8 = HARDWARE IS OVERHEATING
9 = HARDWARE HAS OVERHEATED
10 = EXPANDING
11 = NOT YET AVAILABLE
12 = QUEUED FOR EXPANSION
Any ideas what's wrong ?
Regards,
Gert
I see it's not a problem of 2003. I had the same problem on 2000 systems too.
An example:
HM gives as description:
Message not found. Insertion strings:\Device\CPQCISSE0, Embedded Controller, 1, 5, 0
Eventvwr gives as description:
Logical Drive 1 of Embedded Controller has changed from status code 0 to status code 3.
Status Codes:
0 = OK
1 = FAILED
2 = NOT CONFIGURED
3 = INTERIM RECOVERY MODE
4 = READY FOR RECOVERY
5 = RECOVERING
6 = WRONG PHYSICAL DRIVE REPLACED
7 = PHYSICAL DRIVE NOT PROPERLY CONNECTED
8 = HARDWARE IS OVERHEATING
9 = HARDWARE HAS OVERHEATED
10 = EXPANDING
11 = NOT YET AVAILABLE
12 = QUEUED FOR EXPANSION
Any ideas what's wrong ?
Regards,
Gert
Some applications do not record actually event description, they just record ID of the description that stored in some DLL. If HostMonitor cannot access that DLL, it cannot read description.
If you copy DLL (that specified in the registry under "SYSTEM\CurrentControlSet\Services\EventLog\<Log>\<Event Source>") from remote system to system where HostMonitor is installed and add this registry key as well, it should help
Regards
Alex
If you copy DLL (that specified in the registry under "SYSTEM\CurrentControlSet\Services\EventLog\<Log>\<Event Source>") from remote system to system where HostMonitor is installed and add this registry key as well, it should help
Regards
Alex