Article ID: 284255
Article Last Modified on 2/19/2007
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.
RESOLUTION
To 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
STATUS
Microsoft 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.
MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
This fix allows for the configuration of polling the event logs.
- Start Registry Editor (Regedt32.exe).
- Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNMP_EVENTS\EventLog\Parameters
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: EventLogPollTime(for example, LogLimit)
Data Type: REG_DWORD
Radix: Decimal
Value: Polling value in seconds. The default is to not poll. If polling is desired, set this value to a number that is greater than zero. - Quit Registry Editor.
- Restart the SNMP trap service.
Additional query words: kbNetworking
Keywords: kbhotfixserver kbqfe kbbug kbenv kbfix kbnetwork kbwin2000presp3fix kbwin2000sp3fix KB284255
