Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DHCP Service hangs on startup

Status
Not open for further replies.

brianb000

MIS
Dec 14, 2004
14
0
0
US
I have a W2K Server SP4 box and keep getting Event ID: 7022 in Event Viewer in the System section "The DHCP Server hung on starting". And of course the users cannot get an IP address. All the NIC TCP/IP properties for Default Gateway, IP Address, Subnet Mask, DNS, etc. are correct.

Any Ideas?
 
Maybe reapply the service pack....or reinstall the DHCP service if you have easily resetup the DHCP scopes.

General Description of the 7022 error:



Other people having problems related to the 7022 error...

Ionut Marin (Last update 1/4/2005):
- Service: Messenger - See Q268091.
- Service: User Name mapping - See Q833605.
- Service: SNMP - See Q163595.
- Service: SMS Remote Control Agent - As per Microsft: "This problem may occur if the Systems Management Server site property setting for Windows NT Remote Control is configured to use a protocol that is not installed on the Windows NT target system". See Q191335 for more details.
- Service: Cluster - See "Trend Micro Support Solution ID: 21441".
- Service: Server - See Q266054.
- Service: Backup Exec Job Engine - See the link to "Veritas Support Document ID: 23870".

See the link to "Microsoft event 7022 from source Service Control Manager" for more details on this event.

Alexander Mansson (Last update 11/29/2004):
- Service: OfficeScanNT Personal Firewall - See the link to "Trend Micro Support Solution ID: 22091". If this does not fix your problem, contact Trend Micro.

Ryan C. (Last update 11/8/2004):
- Service: World Wide Web Publishing - In my case, this problem by the fact that the metabase file became corrupt (0 bytes in size). The metabase file is kept in “<system32 dir>\inetsrv\metaBase.bin”. To resolve this problem restore the metabase file from the most recent backup. In my case, this was “metaBase.bin.tmp”. Another place to look is “<system32 dir>\inetsrv\MetaBack”.

Anonymous (Last update 10/19/2004):
- Service: DNS - We have encountered this error under Windows 2000 Server on multiple DCs on an enterprise level network. Despite the “hung” notice, the DNS service will start about 10 minutes later. Microsoft has suggested this may be due to the size of the AD Forest. We were already pushing the limits of AD in 2000 and thus have upgraded to Windows Server 2003. This seems to have helped us get rid of this error.

Yarrokon (Last update 9/17/2004):
- Service: BITS - See Q839091 for information about this problem on Microsoft Windows Server 2003.

Dmitriy Zavgorodniy (Last update 7/16/2004):
- Service: Terminal Services - I received EventID 7022 on the server during an attempt to start the Terminal Services service. According to Microsoft, this behavior can occur if the Terminal Services component is not installed or is disabled. To fix this problem add the Terminal Services component by using the Add/Remove Programs tool in Control Panel before attempting to start the service. For reference, see Q222146.

Anonymous (Last update 1/23/2004):
- Service: McAfee Framework Service - This behavior can occur if the McAfee Framework service takes more than 30 seconds to start. Microsoft Windows NT is designed to log any service taking more than 30 seconds to start as an error. This issue only occurs on some Windows NT systems and is resolved in Windows 2000 and above.

Dave Murphy (Last update 1/23/2004):
- Service: Microsoft Exchange Management: This occurred on a production two-node cluster, running Microsoft Exchange 2000 on one node and SQL 2000 on another. Someone had installed an SQL application that "updated" some system files on node one. During a failover test, from node two, the exchange services could not start on node one. Upon rebooting node one, the 7022 error would appear in the system event log. I re-applied service pack 3 for exchange 2000. The error went away and the service restarted successfully.

Adrian Grigorof
This message indicates that a specific service attempted to start but hung. It is a Service Control Manager message and not a message from the application or service that did not start. Look for more errors from the application or service itself in order to troubleshoot this problem.

- Service: "Background Intelligent Transfer Service" - See Q314862.
- Service: "Commerce Server Predictor" - See Q298550.
- Service: "Computer Browser" - See Q135345.
- Service: "Distributed File System" - See Q307734.
- Service: "Distributed Transaction Coordinator" - See Q290637.
- Service: "Messenger" - See Q224083,Q199352.
- Service: "Microsoft Exchange IMAP4 Service" - See Q233042.
- Service: "Microsoft Exchange Information Store" - See Q308601.
- Service: "Microsoft ISA Server Control Service" - See Q288247.
- Service: "MS Exchange Information Store". See Q308601
- Service: "PRLNTSS.SYS". - See Q129115.
- Service: "Removable Storage" - See Q316500.
- Service: "RPC" - See Q266208.
- Service: "Server" - See Q137399,Q319127.
- Service: "Service Control Manager" - See Q315951.
- Service: "Site Server LDAP Service". See Q317497.
- Service: "SNA DDM" - See Q183556.
- Service: "SNMP" - See Q163595.
- Service: "Windows Internet Name Service" - See Q205100.
- Service: "World Wide Web Publishing" - See Q295162,Q328512,Q278959.

Bjorn
- Services (Several): Exchange and IIS services: The Q322835 article solved my problem.

Jim White
- Service: "Netlogon". See Q315951.

David Dickinson
- Service: World Wide Web Publishing Service. See Q328512.

Stephen Phillips
- Service: "Removable Storage". See MS Article Q316500.

TT Petersen
- Service: License Logging - See Q153140.

Mark Sarria
- Service: World Wide Web Publishing Service. See Q251143.

Rossco
- Service: BITS: I found the Q314862 on Technet regarding this "BITS" service and they have a service pack mini update for download and install. I checked the service prior to installing the update and sure enough it was in "starting" mode for approx 2.5 minutes. Applied the fix and started with no errors in event viewer.

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact (Sales@njcomputernetworks.com)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top