As of right now, I'm unable to debug any of my ASP.NET web application projects on a completely fresh machine because of the error message above. I'm trying for hours now and it's driving me completely nuts because I'm getting paid for working, not for debugging strange environment errors. :/
Installation Procedure / Environment
Installed Windows 8 Professional x64
Installed Visual Studio 2012
Installed Visual Studio 2012 Update 3
Installed IIS through Windows Programs And Features
Nothing else has been done - no addins, no further configuration etc. Administratior permissions are available...
Error message
Unable to attach to application 'webdev.webserver40.exe_00001254_
01ce76431af5c900_dc2119bc-2761-480f-b975-4fab7ad27f390'
(PID: 4692) using '*myhostname*'.
Operation not supported. Uknown error: 0x80040d10.
Do you want to continue anyway?
Same error occurres with Local IIS Web Server (IISExpress too...)
Solutions
In other forums / threads, various solutions have been mentioned, but none of them really fixed it.
Rebooting machine
Reinstalling VS
Terminating running web server instances
Has anyone else faced this annoying error?
Related
I have web app running locally in IIS. App of Net Framework 4.7.2. When I tried "Attach to Process" for w3wp process in Visual studio I am unable to do so. Visual Studio is running under Administrator account. Things I tried:
Restart of IIS and VS in different sequence.
Setting "Enable 32-bit Applications" flag on app pool in IIS to true
Tried to run process monitor to see if there would be errors. Nope, no errors.
Tried manually set type of app in "Attach to" combobox to various types with same results. Types tried: Managed 4.x, with and without Compatibility mode, Managed(Native compilation), Native.
Tried Visual Studio repair - still having issue.
Created brand new web app .Net Framework 4.7.2, deployed it under IIS and tried to attach to the w3wp process and got same issue.
Things I noticed:
When I tried to attached to 64 version of the w3wp the type is "Managed Net 4, x64" and I am getting "Unable connect to the process" message with justification: VS must run as administrator. Funny thing: VS IS running as administrator.
When I turn 32-bit application flag on I am getting type as x86 and plain "Access denied". Even if restart IIS and try to access the app to start new w3wp process. I think it should be: "Managed Net 4, x86", but I am not 100% sure.
At this point I am out of ideas. Any help would greatly appreciated
UPDATE.
I noticed, when I turn on 32bit applications on app pool in IIS I am getting following error in Event Viewer:
"The description for Event ID 0 from source .NET Runtime cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."
Turned out corrupted Avecto installation was the culprit. Reinstalling offending software resolved the issue. Live and learn. At least I lived.:)
My company has an older, Sharepoint-based website hosted on our development environment (Windows Server 2008), managed by IIS 7. Most of the devs in my environment work on these sites by logging into the environment via Remote Desktop, then using the remote Visual Studio 2012 installation.
I don't love using a remote installation of VS for development work, so for the past several weeks, I've been using the following workaround:
I added the drives of our remote environment as network locations on my local machine.
From there, I gave my local Visual Studio 2015 installation the paths as \\{remote_machine_name}\c$\inetpub... etc.
Visual Studio gave me no complaints, and everything went quite smoothly. Today, I had to work with an IIS installation on my local machine. Our company is preparing to switch from Sharepoint to DNN, so I'm doing some preliminary porting and testing on a local installation of DNN using IIS 10. That's when the error started up.
During the configuration process of DNN, I had to change a few lines in the config file at %systemroot%\System32\inetsrv\config\applicationHost.xml. This was because DNN was giving me 500.19 errors after installation. IIS's support said this was likely related to locking of permission regions in this file, and directed me to change the behavior of any locks that gave errors from "Deny" to "Allow".
I can still work via Remote Desktop, but it would be nice to fix this.
I solved the issue by installing IIS 10 using the downloadable installer. I realized I would have to do this when Visual Studio 2015 would not allow me to create any web projects.
I know it's a re-post but I've tried so many different solutions and so far nothing fixed my problem.
I'm having an annoying issue with my Microsoft Visual Studio 2015:
Every time I build my project, I get an alert message saying "Unable to connect to the configured development Web server".
I had an issue when I tried to install MVS 2015 at first but fixed it by disabling the HTTP driver in device manager. After that everything worked great for a week or so, I only had to able/disable the HTTP driver depending on what I wanted to work on. Since today, disabling HTTP doesn't change anything and I always get the same alert message.
My set-up:
HP EliteBook 8560w
Windows 7 professional with Service Pack 1
Intel Core i7-2630QM # 2.00GHz
8.00 GB of RAM
64-bit Operating System
What I've done:
Disabled/Enabled HTTP driver
Install every windows update (windows 7 pro)
Install every MSV 2015 update
Uninstall/Install IIS Express
Delete the automatically generated IIS Express Folder
Inserting this command in Command Shell
netsh http add urlacl url=http://{ip_addr}:{port}/ user=everyone
Opening MVS in administrator
Look if SSL was enabled (it wasn't)
Closing skype or any apps using IIS Express
Close Chrome
And probably more since I got to page 4 of google's results when I searched for this error message.
So yeah, I'm pretty clueless about what to try next, I've read somewhere that installing windows 10 could fix it but I have my doubts about that.
If anyone has any solutions or anything to help me troubleshoot the problem it would be SUPER appreciated!
Thanks,
C.
Update: I should of done a while ago but I forgot, managed to make it work by installing Windows 10.
In my company I'm running Visual Studio 2015 Enterprise and just recently upgraded to Windows 10. Unfortunately, now I can't run any web project using versions of asp.net earlier than 5 (owin/katana) - always getting error :
"Could not load file1or assembly 'XXX' or one of its dependencies.
The process cannot access the file because it is being used by another
process. (Exception from HRESULT: 0x80070020) ".
Now, I've found a few posts like this and the answer is mostly that some other application is running on port 80, 8080 etc blocking visual studio's iis express. The problem is that I get this error regardless of port I'm using (even on some random 34535 etc).
The interesting part is that when I run kestrel (app on asp.net 5) it works and runs fine without any error.
Anyone has any ideas ?
Okay, so I had this issue and resolved it by uninstalling Panda antivirus, which presumably was locking the assemblies for just long enough to interfere with loading them some of the time.
If anyone else is having this issue, and there is definitely an assembly that won't load (as opposed to a port that's already been bound to) then try checking your antivirus!
Few weeks ago I started using VS 2008 (Professional) with Windows 7 (Enterprise).
When working with ASP.Net web applications I repeatedly stumble over the following error:
After opening a solution with a web project the first compilation and debug go perfectly fine. The second time I try to debug the solution I get the "Unable to start debugging on the web server. System call failed" error and solution does not start at all. When I try to debug it again it always shows the same error but sometimes the app actually starts but does not break on the server code at all.
Any ideas why this could happen?
Thanks a lot for any suggestions.
(I use local IIS and run VS as Administrator)
Have you installed SP1 for VS 2008? I am using Win7 as well, and alot of the issues get magically resolved with a service pack. HTH.