I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.
Related
I have an ASP.NET web application that I've been working on for the past few months. Recently I've encountered a problem where when I start debugging and internet explorer launches it locks up. I've tried waiting, but it hangs indefinitely. This happens about 75% of the time. I know it will lock up if the progress bar doesn't show up in the footer. If the progress bar appears then everything works fine. It's turned into a ritual of starting/stopping debugging until it works. If I use Firefox everything works fine. However I can't avoid IE forever as this application is being used in a closed environment where all users are using IE8 exclusively.
I know it's not code related as everything was fine on a Friday, and then with no changes made, it started behaving this way on Monday. I've also opened other web applications and they suffer from the same problem.
I've made sure everything is up to date in Windows Update. I've looked for any updates/fixes to Visual Studio 2010. I haven't been able to find any posts anywhere describing this problem. There's nothing in my logs showing up either.
I'm running Windows 7 SP1 64-bit with VS2010 SP1.
Edit: I've also tried running the solution with IIS instead of the built in dev server, but it had no effect.
I have VS2010 Professional edition and I recently started getting problems debugging an MVC website. The debugging at the Controller code is very slow and each F10 command takes 20 seconds to move to the next line.
Javascript code debugging is quick. I tried a console app and a Forms app and debugging is quick. I also tried creating a blank new MVC app website and the debugger slows down. I am using IIS7.0. This recently started happening as I recently installed VS2012 Ultimate RC. I thought it may be the reason and uninstalled all the software VS2012RC Ultimate installed on that day and the debugger retuned to normal. Looking at task manager devenv.exe was using about 1GB of memory and w3wp.exe was also consuming memory and increasing to 800MB. Has anyone recently installed VS2012 RC Ultimate alongside VS2012 Professional and got into similar problems? Does any one who what is the rootcause of this problem?
Try setting IntelliTrace to collect events only in Options -> IntelliTrace -> General. This might speed up debugging.
When i debug apps on windows7 using VS 2005, it's very slow. just general slowness. works fine on xp.
running outside of the debugger is normal. Even when i start apps outside the debugger then attach and debug it is normal.
im running VS 2005 in Vista compatibility mode.
Any idea what i can do to prevent slowness when debugging?
Seems like the problem happens periodically and is related to the amount and location of breakpoints set in the debugger. The problem can be worked around by attaching to the process after starting it.
For a complete solution, probably need vs2008.
When running the debugger about 50% of the time, Visual Studio 2010 freezes and also locks up my entire machine. I can't even get to Task Manager. Nothing works except my mouse will still move. The only way to recover is to hard boot the machine which takes about 15 minutes each time. I don't have anything else running on my machine at the time except VS, IE 8 (sometimes) and Outlook.
I am running Windows XP on a Lenovo T400 with 3G RAM
Has anyone seen this behavior? If so, how did you fix it?
Thanks,
Rhonda
You don't mention what language your app is but I have run into this with our C++/CLI application on occasion. To avoid it, I changed the Project properties / Debugger and specify "Native" or "Managed" explicitly for the debugger type. The default of "Auto" can get confused.
Also, if you use Application Verifier from Microsoft, I have had VS hang while AV was configured to verify our .exe. To avoid this, we have to launch the app under the debugger as "Native".
The environment:
Clean (new) install of Windows 7 64bit.
Clean (new) install of Visual Studio 2010 Professional (10.0.30319.1).
Windows Update is up to date.
The problem:
I cannot start the debugger on Visual Studio 2010 (hit F5): 'Unable to start debugging on the web server. Unable to connect to the web server. Verify that the web server is running and that incomming HTTP requests are not blocked by a firewall.'
However, 'attach to process' (what I usually do) does work, but it is painfully slow to start (Visual Studio 'thinks' a lot of time before the debugging is actually enabled).
On the same hardware, running VS 2008 on good old Windows XP (32bits), this problem never happened.
Trying to debug a site running under the ASP.NET Development Server also fails: 'Unable to connect to ASP.NET Development Server.'.
There are plenty of web pages about these errors (many very outdated and does not apply to my environment), none of them worked for me.
Notes:
No matter if I run Visual Studio as Administrator or not. The problem is
the same.
The problem happens even when running a brand new blank IIS web site, either created as 'localhost/something' or 'sample.local'.
If I create a 'File System' web site (to try ASP.NET Development Server), when I hit F5, the server starts, but after a long wait Visual Studio says 'Unable to connect to ASP.NET Development Server.'
The 'hosts' file has an explicit 127.0.0.1 entry for 'localhost' and for 'sample.local'
It's the same problem either running .NET 2.0 or 4.0.
It's the same either configuring the application pool with or without 'Enable 32-Bit Applications' true or false.
It's the same either configuring the application pool is classic or integrated mode.
In a desperate attempt, I've added all the IIS 6.0 legacy 'features' stuff (not needed!) and doesn't helped at all.
I don't now what else I can try.
Thanks.
OMG!, I'm so stupid. The most oblivious thing was truly wrong. There was a wrong rule in the firewall. Therefore, even being in 'interactive mode' (as it is was always set), the connection was denied.