Microsoft KB Archive/325840

= The VarBind SNMP Enterprise ID in the SNMP trap conflicts with some service object identifier values that are generated for events that are recorded in the Windows 2000 event log =

Article ID: 325840

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 1

-



This article was previously published under Q325840





SYMPTOMS
When you use the Event to Trap Translator tool (Evntwin.exe) to configure a Simple Network Management Protocol (SNMP) trap, the variable binding (VarBind) SNMP Enterprise ID in the SNMP trap conflicts with some service object identifier (OID) values that are generated for events that are recorded in the Microsoft Windows 2000 event log.



Service pack information
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

File information
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.  Date        Time   Version        Size    File name ---  24-Jul-2002  11:13  5.0.2195.5973  98,576  Evntagnt.dll 12-Jun-2001 16:35  5.0.2195.3727   3,856  Svcpack1.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Windows 2000 Service Pack 4.

