Best IT Recipes

Cannot connect debugger to w3wp

I am debugging an ASP.NET application, but sometimes I can not find w3wp either in the list of Visual Studio processes (Menu: Debug -> Attach to Process... ) or in the task manager . I selected the checkboxes " Show processes from all users " and " Show processes in all sessions ". When you start a project from localhost , after an exception is thrown, the debugger will connect to w3wp (too late for code entry)!

Why sometimes I do not see w3wp?

 Windows Server 2008 Enterprise Edition 64-bit, Visual Studio 2010
+30
debugging w3wp
Nov 30 '10 at 11:26
source share
10 answers

When you reset IIS or IIS do not start, you need to make a call to the server when you first push the server to the w3wp process.

+72
Nov 30 '10 at 11:37
source share

The same thing happened to me. After the update, I could not find W3WP! I realized that he did not show all the processes. You must select the "Show processes from the entire user" checkbox.

+7
Jun 23 '14 at 16:16
source share

The same thing happened to me when I remembered that IIS has an idle timeout! As above, proc w3wp works, but VS2010 looks at it in the idle state and thinks that it does not work, so dos'nt shows it in the list ...

deploying IIS [calling the site served by locahost in your favorite web browser] activates IIS, and suddenly VS can see the process [w3wp] now too

NOTE. - Must ask MS to ignore the IIS / w3wp idle state and if it is in sleep mode - make it automatically wake up!

thank

+5
Apr 19 '11 at 9:20
source share

A quick fix for this when debugging WCF services in Visual Studio:

  • Open the web.config client application file.

  • Locate the endpoint entry for the service that does not appear in the Attach To Process application.

  • Press Ctrl + Click on the endpoint URL to load the service window in the Visual Studio internal browser.

What is it. IIS will start, and now you can return to your service and find W3WP.exe in the process list.

Also make sure that the "Show processes from all users" checkbox is selected.

+3
Sep 11 '13 at 18:32
source share

I also ran into the same problem. Just create the project again. It will then display the w3wp.exe file in the list of attach processes.

+2
Jun 01 2018-12-12T00:
source share

Also, when the window for connecting to the process is open in the lower left corner, the "Show processes from the entire user" checkbox appears, make sure this checkbox is selected, then it will appear. You may also need to run visual studio as an administrator. Hope this helps.

+2
Nov 04 '13 at 19:26
source share

Make sure you run VS as an administrator.

+2
Oct 06 '15 at 8:16
source share

Look carefully at the URL of the page you are debugging from, if it has changed to another server - something that can happen rarely, but happened to me. This falls into the category of "check your assumptions."

+1
Jan 19 '16 at 18:58
source share

I don’t know, but there was an additional application related to the application pool I used. Try creating a new application pool and point your application to the newly created application pool. Double check there is only 1 application with your new application pool.

0
Feb 19 '17 at 16:33
source share

A simple way that works when w3wp does not appear in the list, open a browser and write localhost, then enter. After that, w3wp will appear in the list.

0
May 17 '19 at 9:44
source share


More articles:


All Articles