I'm getting a frustrating error when debugging in Visual Studio 2010.
I'm fairly certain that its something to do with a setting on IIS but no idea what it is!
here is the error:-
'The Web server process that was being debugged has been terminated by IIS.'
The time-out happens every time I debug, on any of the various workspaces we have at work
takes about 90 seconds of inactivity on the debugger for the error to show
IVE FOUND THE SOLUTION
In the advanced application pool settings in IIS you can change the maximum ping response time on the process model to stop the debugger timing out.
Related
Today my CPU Usage Performance profiler in Visual Studio stopped working. I start it, it seems like it's working, you can see the graph of the CPU going up and down but when it finishes I get no data with the message:
"There is no data in the current set of filters."
I have tried every combination of categories and filters with no luck. I restarted Visual Studio, I rebooted the workstation, I tried against a new hello world project. Other performance tools seem to work (e.g. the .NET Object Allocation Tracking tool works). To (try) to rule out that it was something specific in my project I was able to successfully run it on a 2nd workstation against the same set of code. I have also run VS without extensions and also in regular mode after disabling everything I've added in (like ReSharper).
Edit: Additionally I just found this in the Windows Event Viewer.
System.Runtime.InteropServices.COMException: The method or operation is not implemented., System.Object get_Value()
at EnvDTE.Property.get_Value()
at Microsoft.VisualStudio.PerformanceTools.ProjectTarget.LoadBinaryProject(IVsHierarchy hier)
at Microsoft.VisualStudio.PerformanceTools.ProjectTarget.LoadProjInfo()
This also just popped up in the Event Viewer under "Windows Error Reporting" that referenced a Watson VSTelem.Out error:
Fault bucket 125730739576, type 5
Event Name: PerfWatsonVS12Data
Response: Not available
Another oddity is, I just ran a profile session for maybe 20 seconds, however when it's done VS says "Diagnostic session: 127:47 minutes" which would be the about the time I first time I tried it this morning if it never stopped. I did a repair of Visual Studio from the installer and the profile worked for 1 session after, the 2nd session then reverted to the aforementioned behavior again.
I'm currently using:
Visual Studio 16.8.5 16.9.1 16.9.2 16.9.3 16.9.4 16.11.2
.NET Core SDK: 5.0.201
Windows 10 Version 2004 Build 19041.867
Any thoughts on fixes?
Edit: According to the following link, it might be related to a Windows Update and a bug in my NVidia driver:
https://developercommunity.visualstudio.com/t/no-data-in-cpu-usage-tool-windows-update-related/1384519
Microsoft confirmed the problem, as soon as a solution or workaround is found - report it. Follow the forum https://developercommunity.visualstudio.com/t/profiling-cpu-still-states-no-user-code-was-runnin/607535?from=email&viewtype=all#T-ND1373491
Just suddenly over the past day I'm having an issue with Visual Studio 2015 where it takes an age to start debugging anything. Even a simple console application with one line will take over 3 minutes just to start. Running without debugging is normal.
Things I've tried:
Enable Just My Code checked under General Debugging options
Created local cache of Symbols
Removed all Breakpoints
Deleted all user temp files
Reinstalled Visual Sudio
Nothing has had any effect. When starting debugging it just hangs and VS becomes unresponsive for a couple of minutes until it then will start debugging. Once running it is fine. I don't understand why this has suddenly just started happening.
My company have recently pushed McAfee out to all machines, but this has been running on mine for a while now without any issue so not sure why it would suddenly be causing this now. Has anyone else experienced this and if so how did you fix it?
I have disabled Just my code and disabled also diagnostic tools during debug in Tools->settings->debug
Been trying to resolve this issue for a few days now. I've done a ton of searching and tried several solutions - nothing has helped thus far.
I have a Visual Studio 2017 project. It has been running and debugging fine for years now. Suddenly, the other day I can no longer debug the application. Regardless of what browser I select (IE, Edge, Chrome, Firefox, etc) - the same error message is generated:
INET_E_RESOURCE_NOT_FOUND
Also, it takes forever for VS to open the browser to show this message. Additionally, if I start without debugging (ctrl + F5), the site works and loads as expected.
Things I've tried thus far:
Deleting everything from the IIS Express folder in My Documents
Re-installing IIS Express
Repairing IIS
Changing the port number in the project
Various IIS Express reset commands
Resetting IE settings
Clearing caches
There are probably a few others too, but at this point I feel I've exhausted all my options.
Anyone else encounter this and if so how did you fix it?
Thank you for the tip #Fletch Zhou.
Turns out the issue was a corruption in IIS (and likely its certificates). I was able to fix it by following the instructions found here:
Visual Studio 2017 Removing SSL/TLS Connections Problems with IIS Express
One quick note: for projects that already have SSL Enabled set to True, simply toggle the flag and Visual Studio will assign a new SSL port number.
Hope this helps someone else. I know I was frustrated having not made any changes and suddenly I cannot locally debug projects.
More Info: I attempted to debug an application I'd run several times after performing the steps listed in the linked article from PluralSight (tried that several times to ensure I wasn't missing anything). The symptom re-appeared- any browser would indicate the page didn't exist. I noticed that IIS Express was not running - didn't open at all; or at least not noticeably. I unchecked the "Enable Edit and Continue" option as discussed in this post: IIS Express Immediately Shutting Down Running Site after Stopping Web Application. Though the symptoms didn't match exactly, it was a simple-enough option to try. Sure enough, the site was operational once again. I'm running Visual Studio 2017 Version 15.6.4. Not sure if this is related to Visual Studio or IIS Express, but unchecking the "Enable Edit and Continue" seemed to resolve the latest hang up.
I had to set my start page to Default.aspx again. I don't know how it got unset or why it would result in that INET_E_RESOURCE_NOT_FOUND error.
I am running into a frustrating issue with Visual Studio in which every time I open or refresh a solution, Visual Studio locks up for about 30 seconds and then I am met with this error
This happens about 10 times, so it takes about five minutes to get a working instance of Visual Studio.
I eventually traced this to entries in Server Explorer to which I don't have access. These seem to be auto-populated from connection string entries in various Web.config files throughout the solution. If I comment out the connection strings, the solution loads fine. But this is not an ideal solution because I don't want to commit these changes to source control.
Is there a way to stop this auto-population of Server Explorer? I don't remember this ever happening in previous version of Visual Studio, so maybe it's new in 2015?
I get the following error sometimes when deploying a SharePoint 2010 solution via Visual Studio 2010:
Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.
It's true -- it's taking a long time because we do a lot of work in the feature receiver. But This is not an error; I would just like Visual Studio to wait longer. Is there a place I can configure the amount of time to wait before timing out?
ChannelOperationTimeout
http://msdn.microsoft.com/en-us/library/ee471440.aspx
Do not forget to restart Visual Studio