IIS: Services Fail to Start with Event ID 7023 (327649)


The information in this article applies to:

  • Microsoft Internet Information Services 5.0
  • Microsoft Internet Information Server 4.0
This article was previously published under Q327649
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:

http://www.microsoft.com/technet/security/prodtech/IIS.mspx

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

After you restart your server that is running Internet Information Server (IIS) 4.0 or Internet Information Services (IIS) 5.0, services such as the World Wide Web Publishing Service, the Simple Mail Transfer Protocol (SMTP) Service, and the FTP Publishing Service may not start. In your Event Viewer system log, you may see a corresponding error message similar to the following for each service that did not successfully start:
Event ID: 7023
Source: Service Control Manager
The World Wide Web Publishing Service service terminated with the following error: Not enough resources are available to complete this operation.
-or-
Event ID: 7023
Source: Service Control Manager
The World Wide Web Publishing Service service terminated with the following error: The parameter is incorrect.
-or-
Event ID: 7023
Source: Service Control Manager
The Simple Mail Transport Protocol (SMTP) service terminated with the following error:
Not enough resources are available to complete this operation.
-or-
Event ID: 7023
Source: Service Control Manager
The Simple Mail Transport Protocol (SMTP) service terminated with the following error: The parameter is incorrect.
-or-
Event ID: 7023
Source: Service Control Manager
The FTP Publishing Service service terminated with the following error:
Not enough resources are available to complete this operation.
-or-
Event ID: 7023
Source: Service Control Manager
The FTP Publishing Service service terminated with the following error: The parameter is incorrect.


If you try to manually start the service from the Services applet in Administrative Tools, you may receive one of the following error messages:
Could not start the World Wide Web Publishing Service service on Local Computer.
Error 1721: Not enough resources are available to complete this operation.
-or-
Could not start the Simple Mail Transport Protocol(SMTP) service on Local Computer.
Error 1721: Not enough resources are available to complete this operation.
-or-
Could not start the FTP Publishing Service service on Local Computer.
Error 1721: Not enough resources are available to complete this operation.
If you try to start the services from the command prompt, you receive one of the following error messages:
C:\> net start w3svc
The World Wide Web Publishing Service service is starting.
The World Wide Web Publishing Service service could not be started.
A system error has occurred.
System error 1721 has occurred.
Not enough resources are available to complete this operation.
-or-
C:\> net start msftpsvc
The FTP Publishing Service service is starting.
The FTP Publishing Service service could not be started.
A system error has occurred.
System error 1721 has occurred.
Not enough resources are available to complete this operation.
-or-
C:\> net start smtpsvc
The Simple Mail Transport Protocol (SMTP) service is starting.
The Simple Mail Transport Protocol (SMTP) service could not be started.
A system error has occurred.
System error 1721 has occurred.
Not enough resources are available to complete this operation.

CAUSE

This problem may occur if the Microsoft Distributed Transaction Coordinator (MSDTC) has been configured to use a certain range of ports for incoming requests, but the range that has been specified is not large enough.

RESOLUTION

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.

If you do not have to specify which ports MSDTC uses, you can resolve this problem by deleting the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet

  1. Click Start, click Run, type regedt32 in the Open box, and then click OK. This starts Registry Editor.
  2. In Registry Editor, expand HKEY_LOCAL_MACHINE.
  3. Under HKEY_LOCAL_MACHINE, double-click Software, double-click Microsoft, and then double-click Rpc.
  4. Under RPC, select Internet.
  5. On the Edit menu, click Delete to delete the key.
  6. On the File menu, click Exit to close Registry Editor.
  7. Click Start, and then click Shut Down. Select Restart in the list, and then click OK to restart the computer.
If you must control which ports MSDTC dynamically allocates for incoming communication, you must increase the number of ports that are specified under that registry key:
  1. Click Start, click Run, type regedt32 in the Open box, and then click OK. This starts Registry Editor.
  2. In Registry Editor, expand HKEY_LOCAL_MACHINE.
  3. Under HKEY_LOCAL_MACHINE, double-click Software, double-click Microsoft, and then double-click Rpc.
  4. Under RPC, select Internet.
  5. In the right pane, double-click Ports.
  6. In the Multi-String Editor dialog box, increase the range of specified ports. For example, if the current range is from 10000-15000, which allocates 5,000 ports, you can change the range to 10000-20000 to allocate 10,000 ports.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

    250367 INFO: Configuring Microsoft Distributed Transaction Coordinator (DTC) to Work Through a Firewall

  7. On the File menu, click Exit to close Registry Editor.
  8. Click Start, and then click Shut Down. Select Restart in the list, and then click OK to restart the computer.

MORE INFORMATION

By default, the Internet key and its values under HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc do not appear in the registry. If this key exists, it was probably added to specify the ports that the MSDTC allocates. This is most frequently done to permit MSDTC to work through a firewall.
Modification Type:MinorLast Reviewed:6/23/2005
Keywords:kbpending kbprb KB327649
©2004 Microsoft Corporation. All rights reserved.