Databases
StackOverflow2013
Postsdbo
POVisual Studio Debugger 2010 - Can't Connect to webdev process
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio Debugger 2010 - Can't Connect to webdev process
    primarykey
    data
    text
    <p>I've searched all over the internet for a situation that is similar to mine. Ive found nothing.</p> <p>I have MS VS 2010 Pro on Windows 7.</p> <p>My problem is that I cannot connect the debugger to the WebDev.WebServer40.EXE worker process. If I click the green debug button, firefox (or IE) opens, but immediately displayed a "Cannot connect to server" and the VS acts as if the button was never pressed.<br> If I right click a file name and click "view in browser", everything works fine. If I then try to attach to the process manually, the process is killed (watching the task manager) and I get the same error as if I hit the debug button.</p> <p>Now, I can export my web application and open it with IIS under localhost. When I do that, I can connect to the w2wp.exe worker process and debug that way.</p> <p>Also, I can't debug any console apps. Not screen appears.</p> <p>There is no good information in the output window.</p> <p>I can't find any good errors in the event viewer.</p> <p>This all started recently. Previously it worked fine. The only thing I did in the last couple of days was uninstall and reinstall visual SVN. Currently it is uninstalled. I also did the full repair on Visual Studio to try and fix the issue. I can't think I anything else to try...</p> <p>(Note, I also have VS 2012 RC installed on the machine. It gets the same exact issues).</p> <p><b>TLTR</b> VS Debugger can't connect to it's own worker process (the process crashes on attempting). But it can connect to the IIS w3wp.exe worker process. What the.....?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USlorengphd
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThis may or may not be the issue but I had this happen to me once because my path variable got too long (thus visual studio dependent commands didn't work anymore). The error was never obvious but I was able to link it back to the path variable because of a recent install I had done. This probably won't help but its just a thought... Also, did you take a look at this question? http://stackoverflow.com/questions/3950865/cannot-start-debugger-on-visual-studio-2010-f5-however-attach-to-process-d?rq=1
      singulars
      1. POVisual Studio Debugger 2010 - Can't Connect to webdev process
      1. UStheMothaShip
    2. COThanks for the ideas. I haven't changed any path variables. I did see that post, but the problem tends to be different. Plus, I don't have a firewall set up.
      singulars
      1. POVisual Studio Debugger 2010 - Can't Connect to webdev process
      1. USlorengphd
    3. COI just did a full reinstall of visual studio. I ran ccCleaner to clean the registry. The problem still persists.
      singulars
      1. POVisual Studio Debugger 2010 - Can't Connect to webdev process
      1. USlorengphd
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload