[ZBX-8723] Some Messages cannot be gotten from eventlog using Message.dll Created: 2014 Sep 05  Updated: 2019 Dec 10

Status: Open
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 1.8.20, 2.0.12
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Yoshinori Komuro Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: eventlog, windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows

Attachments: JPEG File custom_zabbix.jpg     JPEG File eventlog.jpg     XML File eventlog.xml     JPEG File original_zabbixweb.jpg    

 Description   

This issue is different from ZBX-8595.

original_zabbixweb.jpg shows the message gotten by the original Agent.
The wrong message was gotten from system message-table resources.

custom_zabbix.jpg shows the message gotten by the patched Agent which cannot the correct message either.

At this time, I found another issue. When I checked Qualifiers of the event record, Qualifiers is not set.
But I think Qualifiers(0x0100) is needed for this record.

The problem occurs when the event refers to advapi32.dll without setting Qualifiers(0x0100).
I think Qualifiers(0x0100) should be set.

 Comments   
Comment by Yoshinori Komuro [ 2014 Sep 08 ]

I'm Sorry to be poor at English.
Please correct a message.

  • Title
    Some Messages cannot be gotten from eventlog using Message.dll.

-Description
This issue is different from ZBX-8595.

[original_zabbixweb.jpg] shows the message gotten by the original Agent.
The wrong message was gotten from system message-table resources.

[custom_zabbix.jpg] shows the message gotten by the patched Agent which cannot the correct message either.

At this time, I found another issue. When I checked Qualifiers of the event record, Qualifiers is not set.
But I think Qualifiers(0x0100) is needed for this record.

The problem occurs when the event refers to advapi32.dll without setting Qualifiers(0x0100).
I think Qualifiers(0x0100) should be set.

sasha It's corrected. Thank you.

Generated at Fri Apr 26 04:30:12 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.