SNMP Event to Trap Translator Does Not Read all Event Log Messages (284255)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q284255 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you are using the SNMP Event To Trap translator that is included with Windows 2000 to monitor events in the Event log, some events that should have traps sent for them may not have traps sent for a very long time. This can occur if events come into the Event log at a very fast rate. The SNMP Event Agent is not notified for every new event that is logged when events come into the log at a very fast rate. The SNMP agent interprets that it will always receive notification and is waiting forever for this notification. Because the SNMP Event Agent does not poll for new events, there may be new events that the agent was not notified about. The SNMP agent is notified when a new event comes into the log and a trap is sent, but that is dependent on a new event being logged which may introduce a long delay.
CAUSE
The SNMP agent does not poll for new events.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later: Date Time Version Size File name
-------------------------------------------------------
2/7/2001 01:53p 5.0.2195.3227 97552 Evntagnt.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbenv kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB284255 |
---|
|