Article ID: 158770 - Last Review: February 27, 2007 - Revision: 2.2

SNMP Service Will Not Start with Event ID: 7024

View products that this article applies to.

This article was previously published under Q158770

Expand all | Collapse all

SYMPTOMS

The SNMP service fails to start and displays the following message:

EVENT ID: 7024
Description: The SNMP Service terminated with service specific error 3.

Back to the top

One possible cause of this error is that another application may be binding to the same port as the SNMP Service. An easy way to determine if this is the problem is to change the port number that the SNMP service binds to. If this resolves the issue look, for any third-party applications that may be using the same port number.

Change to the %SystemRoot%\System32 subdirectory.
Rename the SNMP.exe in your %SystemRoot%\System32 subdirectory to Snmp.fre.
Copy the checked build of Snmp.exe file to your %SystemRoot%\System32 subdirectory.
From a command prompt type the following:
NET START SNMP /loglevel:20 /logtype:7

NOTE: For Windows NT 4.0, use the following line to start the SNMP service:

NET START SNMP /loglevel:5 /logtype:2

To change the port number that the SNMP service binds to, use a text editor (such as Notepad.exe) to edit the Services file located in the Windows System32\Drivers\Etc folder.

The default ports in the services file are:

snmp 161/udp snmp
snmp 162/udp snmp-trap

For testing purposes change to:

snmp 165/udp snmp
snmp-trap 166/udp snmp

For example,

   # Copyright (c) 1993-1994 Microsoft Corp.
   #
   # This file contains port numbers for well-known services as defined by
   # RFC 1060 (Assigned Numbers).
   #
   # Format:
   #
   # <service name>  <port number>/<protocol>  [aliases...]   [#<comment>]
   #

   snmp     165/udp  snmp
   snmp-trap   166/udp  snmp

NOTE: Remember to change the values back after you are done testing.

Back to the top