Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Restarting the ISA Server Control Service Uses 100% of CPU

Restarting the ISA Server Control Service Uses 100% of CPU

View products that this article applies to.

This article was previously published under Q323559
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� (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry

↑ Back to the top

Symptoms

If you use the Internet Security and Acceleration (ISA) Server snap-in in Microsoft Management Console (MMC) to restart the ISA Control service, you may receive the following error message:
1053 - The service did not respond to the start or control request in a timely fashion.
When this occurs, you see in Windows Task Manager that Services.exe is using 100 percent of the CPU resources. Performance at the console is sluggish. Internal users may lose the ability to access the Internet through ISA Server. Internet uses may lose the ability to access any servers that are published by ISA Server. The server stops responding (hangs) for an indefinite period. You may not be able to shut down the server gracefully; you may have to force a restart by either turning off the ISA Server-based computer or unplugging it.

↑ Back to the top

Workaround

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.

To work around this issue:
  1. Click Start, click Run, type regedt32, and then click OK.
  2. Locate and then click the following registry key:
    Hkey_Local_Machine\System\CurrentControlSet\Services\ISACTRL
  3. In the right pane, double-click the DependOnService value. The DependOnService value shows the following services:
    Rasman
    Mspfltex
    WMI
  4. Remove Rasman from the list of services. Leave Mspfltex and WMI.

↑ Back to the top

Keywords: KB323559, kbprb, kbenv

↑ Back to the top

Article Info
Article ID : 323559
Revision : 2
Created on : 10/31/2006
Published on : 10/31/2006
Exists online : False
Views : 270