I am running Windows 10 Pro (10.0.16299). IIS Manager missing and web app returns HTTP error 503
I am IIS Manager 7 as a web server for my web app. The default MSFT web site comes up but my web app returns error 403. Tried to find iis manager, but it is nowhere to be seen. I see it in control panel but double-clicking does not start anything.
This was working last Friday and it is not on following Tuesday. Our IT installs patches using some other way, I am not able to Windows Update.
In Windows Features, teh checkboxes are checked, seems to imply it is installed. Tried to uncheck those to remove and add them back, but the removal returned error 0x80073712. Running .NET Framework 4.7.
Any thoughts would be helpful. If I can start it up, maybe fix it.
Related
The WWW Pub Service was working fine before I installed the Win10 Fall Creators Update.
Now I get this error
HTTP Error 503. The service is unavailable.
I'm simply trying to load a local web page with a browser (simple html, not asp.net page).
http://localhost/html/home/index.html
Edge and Firefox give the same error.
Is there anything in the Win10 FCU that would have made config changes in IIS?
PS. I also installed the latest version of Visual Studio Community ed 2017. But I don't think that should have affected IIS.
Stop “Windows Process Activation Service” and “W3SVC” service and clean out (delete) all the files under C:\Inetpub\temp\AppPools*. Start your services and the sites should be back to work.
Source: https://www.ajeetyelandur.com/2017/10/Windows-10-Fall-Creators-update-crashes-App-Pool/
I am struggling with this very popular error. I believe I have looked at the related questions and not found one that fits my problem.
I have a visual studio 2013 webapi project that I am trying to run. This code works fine for other team members.
My computer is windows 7, and I haven't previously had any problems running web sites locally.
If I run in debug, I get "Unable to start debugging on the web server"
If I start without debugging I get "{
"ErrorMessage": "The resource you requested was not found."
}"
This only happens running as "local IIS". If I select "IISExpress" it runs perfectly well (but on a port).
I have tried:
Checking the app pool is .net 4
Changing the identity of the app pool to my login
stopping and starting the app pool
checking the permissions on the local folder
commenting out all the code in Application_Start of the Global.asax
Any other suggestions would be most welcome
I'm using Visual Studio 2013 with IIS Express 8 to develop an application for a local Intranet. This application was built using ASP.NET MVC 4 in Visual Studio 2012 and later migrated to 2013. I had been using Visual Studio Development Server until I migrated to VS2013 with no issues.
After the migration, the application compiles, runs and authenticates fine, but it's not serving Static Files - it just returns an HTTP 500 response with no further details. See image below:
This also happens to Images and CSS files.
What can I check to solve this? Any suggestions?
UPDATE:
The application works fine in Local IIS (version 8).
It works in IIS Express on other PCs.
UPDATE 2:
After further testing, I found out that this only happens to Mozilla Firefox (it works fine in Internet Explorer and Google Chrome) - I didn't notice before because I always use FF. Currently using version 29.
Any ideas?
Finally! I was able to solve this issue with the help of this question.
This was happening because Firefox by default has Windows Integrated Authentication turned off. It doesn't make any sense to me why it works fine in regular IIS or in dynamic files (controller actions, WebApi, etc.), but that's a mystery for another day.
To enable Windows Integrated Authentication I followed this steps:
Type about:config in Firefox's address bar (nav bar)
Search for network.automatic-ntlm-auth.trusted-uris
Double click on network.automatic-ntlm-auth.trusted-uris
Add http://localhost to the list (paste that if it's empty)
After that I just hit F5 in Firefox and everything worked as expected.
This issue is poorly documented, so I wonder if nobody else uses Firefox with MVC to develop web applications using Windows Integrated Authentication?
Have you had a look at this ?
ASP.NET MVC application gives Internal Server Error only when viewed in Firefox
It doesn't explain why it works on IIS but there is a firefox doesn't support Integration Authentication out of the box.
The only thing that seems applicable to your situation is a problem with the install of IIS Express since this is an similar issue to something seen in previous IIS Express versions. I would either re-install it or see if your version of Windows can host IIS 8 in which you would just enable static content.
If this was just a matter of not having static content turned on or permissions for static content, you'd get a 404 or 401 error respectively. Hope this helps...
I'd look in the machine events viewer under application and system to see what the issue is.
Does the IIS serve anything up in the same folder such as .txt files, .html, jpg images?
It could possible be file or folder permission and/or the anonymous user being used to access them under IIS.
My first point would be event viewer though for more detailed information on the 500 error.
So I've been working at this for about 2 days now and have essentially hit a dead end. I guess the first thing to know is, can IIS Express work in combination with Visual Studio 2010 and Windows 8?
I just got this new laptop in, with Windows 8 pre-installed. I installed Visual Studio 2010 Ultimate, SP1, and MVC 3. I had to enabled .NET Framework 4.0 myself...
I have a project that I transferred from my old computer (windows 7) to this computer. It was set up to run on IIS Express. So when I opened the project, VS2010 said that I was missing some components and asked if I wanted to install them--so it installed IIS Express for me. When I try to run my project, I get a "This page can't be displayed" page in IE. In fiddler, I get
- 302 HTTP localhost:16683 /
- 502 HTTP Tunnel to localhost:443
the SSL URL for the project is https://localhost:44300/
the URL for the project is http://localhost:16683/
If I go to IISExpress in my system tray and select the https link there, it opens the website up just fine. If I select the http link there, it get that "502 HTTP Tunnel to localhost:443" line in fiddler again... Why is it trying to tunnel to localhost:443???
Another thing to note is that I decided to create a test MVC 3 project from scratch to see what IIS Express would do. I set the project to run on IIS without enabling SSL. When I run the project is starts up just fine. When I click the logon link, it tries to redirect to an https link with port 44300...when it shouldn't be. I created a test project for the same purpose on my windows 7 machine, and the project did not do this.
The last thing to note is that after going to the https link for my initial project via the IIS Express tray icon, if I click the logon link for the test project, it now takes me to my initial project's https link... It's as if the projects are crossing over into each other...
I have a newly installed laptop running Win7/x64 and installed Visual Studio 2010, then VS2010 SP1, and then the Windows Azure SDK 1.4.
When I attempt to debug a cloud service project in the local compute emulator environment, I get an error: "The was an error attaching the debugger to the IIS worker process for URL 'http://127.0.0.1:5102/' for role instance..."
Some searching turned up quite a few discussions on this issue with the Azure SDK 1.3 update and I've narrowed down the issue to my having multiple sites in the same Web Role in my Azure application. If I comment out the sites entries in the ServiceDefinition.csdef, there's no error and debugging works fine. I tried the other recommended solutions, reinstalling .NET, re-registering ASP, rebooting while facing Redmond, but same problem.
I'm surprised by this issue on a new VS/Azure 1.4 installation and I'm hoping someone else has resolved supporting multiple sites for local debug.
Thanks!
I ran into the same problem, and have two suggestions:
If you've pointed to the "Published" output of a website and not the source location in ServiceDefinition.csdef, you'll get this error. Point to the source location of the web site when you're debugging. You can always switch the location later if you'd rather deploy a published web site rather than the source.
Ensure that you have debug set to false in the each of the web application's web.config file. While obvious, this catches me from time to time.