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.:)
Related
I am setting up my new workstation (Windows 10 Pro) with my ASP.NET projects with Visual Studio 2017. I have enabled local IIS and the project throws a timeout error while trying to debug the project.
It is not failing 100% of the time though, mostly fails but when it runs it is taking longer than expected to give the startup page. The error thrown is
Unable to start debugging on the web server. The operation has timed out
I did notice that the IIS worker process (w3wp.exe) was only executed in the completed console output. So it looks like the IIS worker process is not always being executed.
Any help would be appreciated!
Thank you!
The project runs successfully on an old workstation (Windows 10 Edu) with Visual Studio 2017. App pool settings has been compared between both and it seems same. IIS reset is tried as well. Visual studio has been repaired and IIS local has been restarted as well (unchecking and enabling followed by restarting the machine). Default app pool is used and its been recycled as well. Nothing worked!
Possibly the Visual Studio project version does not match the ASP.NET configured application pool. Update the ASP.NET version in the application pool and restart it.
Make sure you have the correct version of ASP.NET installed on IIS. A version mismatch between ASP.NET in IIS and the Visual Studio project can cause this issue. May need to set the framework version in web.config. To install ASP.NET on IIS, use the Web Platform Installer (WebPI).
If the issue is not related to IIS configuration, try the following steps:
Restart Visual Studio with administrator privileges and try again.
For example, using the Web to deploy some ASP.NET debugging scenarios that require elevated Visual Studio privileges.
If you are running multiple instances of Visual Studio, reopen your project in one instance of Visual Studio (with administrator privileges) and try again.
If using a HOSTS file with a local address, try using the loopback address instead of the computer's IP address.
If not using a local address, make sure the HOSTS file contains the same project URL as in the project properties, Properties > Web > Server or Properties > Debug, depending on the project type.
Reference link:
Visual Studio "Unable to start debugging on the web server. The web server did not respond in a timely manner.".
I've created an ASP WebForm application that requires "Enable 32-Bit Applications" to be set to true. When I set the site up in IIS I set "Enable 32-Bit Applications" true, but when I look at the Task Manager I'm not seeing the *32 next to the w3wp.exe process that starts up. And when I browse to the site I'm getting "Service Unavailable - HTTP Error 503. The service is unavailable." as the App Pool stops within IIS.
How can I force the w3wp.exe process to start in 32 bit mode?
EDIT- The machine in question is a 64-bit Windows Server 2012 R2 in case that matters
EDIT 2- I found a link to http://www.manasbhardwaj.net/running-32-bit-web-application-iis-8/ Which references issues wile Running Sharepoint 2013, Which is running on the web server. It applied the changes, and now when I run the site I get a configuration Error regarding framework versions.
I find it odd b/c the app pool still is not showing the *32 next to it, but it didn't crash when starting the site.
I'm going to ensure the latest .NET framework is installed now.
EDIT 3- Looks like I need to run a couple of updates on the machine in order to install the latest .NET framework. The .NET framework my site uses is 4.6.1, Is this version Stable enough to run on a Live WebServer running SharePoint 2013?
I have an ASP.NET web site created with WebMatrix 3. I do have the option in VS2013 checked to use the 64-bit version of IIS Express since I am running on 64-bit Windows 8.1. When I try to launch the project I get the error "An operation is not legal in the current state". Does anybody know how to fix this?
I got this same error "An operation is not legal in the current state" when running a project on Google Chrome, Stopping the project then closing all chrome instances fixed the problem.
I think it's related to visual studio not being able to attach to chrome instance for debugging.
Closing Chrome and restarting IIS (e.g. in IIS Manager) should solve the issue. It helped in my case.
Just had the same issue on VS (Visual Studio) 2017 this morning.
The steps that will resolve this are:
Stop project that runs in VS
Clean all IIS instances that VS temporarily created
Compile project and start that service again
I'm getting the following error after installing VS2013:
Service Unavailable HTTP 503
The earlier version of IIS is working with an application pool ASP.Net 4.0. This uses the 4.0 framework. I believe the new version uses the 4.5.1 framework. So the application pool might get a conflict. So when I go through the IIS manager dashboard I noticed that the application pool is getting stopped automatically. So I manually restarted and tried again. Whenever the application starts this application pool get stopped automatically. I don't know why this happening?
Please could you help to fix this issue?
I am not quiet sure whether it works for you, but i had the similar problem once, registering the FrameWork with the IIS Manager resolved my problem.
Below are the commands to run depending on 64-bit/32-bit OS version installed in your system
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
Note:
1. Please remember to replace the "v4.0.30319" with your current version installed.
2. You should run the above commands as a Administrator(better if you logged in as a administrator).
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?