Error message when you restart a domain controller that is configured as a Systems Management Server 2003 management point: "MP Control Manager detected MP is not responding to HTTP requests"

When you restart a computer that is configured as a Microsoft Systems Management Server (SMS) 2003 management point, you experience the following symptoms:

• The management point does not start, and you receive the following error message:
  MP Control Manager detected MP is not responding to HTTP requests. The HTTP error is: Service Unavailable
• The following events are logged in the System log:

  Event Type: Error
  Event Source: W3SVC
  Event Category: None
  Event ID: 1059
  Date: date
  Time: time
  User: N/A
  Computer: ServerName
  Description: A failure was encountered while launching the process serving application pool 'ApplicationPoolName'. The application pool has been disabled.

  Event Type: Warning
  Event Source: W3SVC
  Event Category: None
  Event ID: 1057
  Date: date
  Time: time
  User: N/A
  Computer: ServerName
  Description: The identity of application pool 'ApplicationPoolName' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool. Therefore, the application pool has been disabled.

• The following event is logged in the Directory Service log:

  Event Type: Error
  Event Source: NTDS General
  Event Category: (18)
  Event ID: 1126
  Date: date
  Time: time
  User: N/A
  Computer: ServerName
  Description: Unable to establish connection with global catalog.

You may experience this problem when the following conditions are true:

• The SMS 2003 management point is configured on a domain controller.
• The domain controller is isolated on a slow site link.

This problem occurs if the Net Logon service on the domain controller does not start before the World Wide Web Publishing Service starts.

The SMS Management Point Pool application pool does not start if Windows cannot verify the identity of the account under which the application pool starts. On a domain controller, the identity for this application pool is the Example\IWAM_ServerName account. If the Net Logon service cannot verify this account before the World Wide Web Publishing Service starts, the SMS Management Point Pool does not start successfully.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem, configure the IIS Admin Service to depend on the DNS Server service and on the Net Logon service. If the domain controller starts in a location that is connected only by a slow link, some latency may occur when the Net Logon service starts and when the DNS Server service starts. If you configure the IIS Admin Service to depend on the Net Logon service and on the DNS Server service, the World Wide Web Publishing Service and the W3SVC Worker Processes that host the Out of Process application pools cannot start before Windows verifies the application pool identity.

To configure this dependency, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IISADMIN
3. In the right pane, right-click DependOnService, and then click Modify.
4. In the Edit Multi-String dialog box, type Netlogon in the Value data box, and then press ENTER.
5. In the Value data box, type DNS, and then press ENTER. The contents of the Value data box appear as follows:
   RPCSS
   SamSS
   Netlogon
   DNS
6. Click OK, and then exit Registry Editor.

For more information about how to create service dependencies, click the following article number to view the article in the Microsoft Knowledge Base: