Remove Timeout When Debugging w3wp Process

One of the smart guys I work with posted some information about debugging the W3WP process that I though I should share. Many times when debugging this process I get timeout errors when I let it sit for too long.

Error: The web server process that was being debugged has been terminated by Internet Information Services (IIS)

You can get rid of the timeout by following the following directions. Caution, this should only be done on development boxes, do not change these settings on your production machines.

  1. Open the Administrative Tools window.
  2. Click Start and then choose Control Panel.
  3. In Control Panel, choose Switch to Classic View, if necessary, and then double-click Administrative Tools.
  4. In the Administrative Tools window, double-click Internet Information Services (IIS) Manager.
  5. In the Internet Information Services (IIS) Manager window, expand the node.
  6. Under the node, right-click Application Pools.
  7. In the Application Pools list, right-click the name of the pool your application runs in, and then click Advanced Settings.
  8. In the Advanced Settings dialog box, locate the Process Model section and chose one of the following actions:
    • Set Ping Enabled to False. —or—
    • Set Ping Maximum Response Time to a value greater than 90 seconds.
  9. Setting Ping Enabled to False stops IIS from checking whether the worker process is still running and keeps the worker process alive until you stop your debugged process. Setting Ping Maximum Response Time to a large value allows IIS to continue monitoring the worker process.
  10. Click OK.


Popular posts from this blog

Add User As Local Administrator On Domain Controller

Calling Dataverse Web API in PowerShell using Client Credentials

Windows Server 2008R2 VMs Shut Down After 1 to 2 Hours