Windows 8.1 / Windows 10 breaks my ASP.NET / IIS : "Service unavailable" - url-rewrite-module

With Windows 8.1 finally released to MSDN/Technet today I came across the following issue running my ASP.NET application after doing an in place upgrade with Win 8.1 RTM:
Service Unavailable
HTTP Error 503. The service is unavailable.
The AppPool has died and shows a status of Stopped
The IIS log has nothing
There's a clue is in the Windows Application log which contains this error
The Module DLL C:\WINDOWS\system32\inetsrv\rewrite.dll failed to load. The data is the error.
How can I recover my IIS to make it work again?

It looks like a simple uninstall and re-install of the rewrite module will do the trick.
Edit: As others have said - try a repair first - if it works then that should be faster.
It doesn't look like the Microsoft Web Platform Installer is able to uninstall it so just go to Programs and Features to uninstall it.
You'll find it listed as IIS URL Rewrite Module 2 and just click the Uninstall button on top.
Then reinstall it from here:
http://www.iis.net/downloads/microsoft/url-rewrite
Make sure your App Pool is started - or just restart IIS and it should all work again.
Edit: 8/30/16 : A similar but unrelated error can occur if you have the 'new' .NET core installed and update to Win 10 Anniversary edition. See here: https://github.com/aspnet/Home/issues/1583 - Running a repair on VS 2015 Tooling Preview should fix it. Wanted to add it here since the errors are very similar to this answer.

I got this Event Log error after updating Win8.1 to Win10. To fix, go to the Control Panel -> Programs and Features, locate IIS URL Rewrite Module 2, right click and select Repair (it's quick). Next, restart your stopped AppPool(s). Should be OK now.
No need to uninstall nor reinstall.
Gary Davis

Don't need to uninstall. Just do a Repair instead, and it will works.

For some weird reasons, the only solution for me was to install previous version of the module, from https://www.microsoft.com/en-us/download/details.aspx?id=7435

I just ran in to this issue after an update. All of the app pools where stopped!
Starting them resolved the issue.

I struggled with similar issues last night.
It started out with a complaint about missing redirect.dll. After installing IIS' Redirect feature, that log message disappeared and all I was left with was a bunch of error messages from WAS. It tried starting my application pool five times until giving up.
A listener channel for protocol 'http' in worker process '120' serving
application pool 'my app pool' reported a listener channel failure.
The data field contains the error number.
The error code was "8007007E" (File not found according to google).
I then installed ProcMon from sysinternals.com and every time the w3wp process complained about "NAME NOT FOUND" right before terminating, I googled and installed the corresponding IIS feature. I repeated this until I had installed them all and got everything working again.
Installing everything is not a good solution, but I do not have time to investigate deeper right now.

I came across similar symptoms after changing my domain password. I had to also reset my password in my (hard coded!) App Pool settings on my dev box.

I had a similar issue with "httpplatformhandler.dll failed to load". Again the solution was to download the appropriate httpplatformhandler install msi from http://www.iis.net/downloads/microsoft/httpplatformhandler and then run a repair.

The Repair worked for me after updating to W10 Insider Preview 160826-1902

I encountered the same problem in Windows Server 2012 R2. After I update Windows Updates to newest, it works.

Related

.Net core 3.1 sudenly stoped thowing HTTP Error 500.31 - ANCM Failed to Find Native Dependencies

Everything was fine until yesterday. This must be due to Windows update. No one touched the server. I have tired couple of similar solutions posted in Stack Overflow(all are old questions),none of them worked for me. What I have, Server Windows server 2019, APP netcore 3.1 ,IIS version 10. .net core runtime and SDK both are installed. This was working before. No one touched anything, just stopped working
In the browser appearing
HTTP Error 500.31 - ANCM Failed to Find Native Dependencies
When I executed on the command line
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in
When I checked event log. Something like below appeared. But let me tell you in the build
directory we don't have a file like app.runtimeconfig.json
What I have tried
Repair .netcoe runtime and SDK
Restore old DB backup
Reinstall .netcore versions
No pending Windows updates
Restart IIS APP pool also the server
Check file permission
None of them worked for me. If anyone can help, really appreciate.
For this issue, we can't find out that the environment of windows server caused by windows update is abnormal. As you said, it worked fine before.
So please allow me summarize below suggestions as answer.
Suggestions
Copy the publish file named original_file . And paste it in our dev pc or other server which have IIS Management. And test it, this publish file should be works. This step just confirm the publish file is normal.
Create a new website and a new application pool. Create a new asp.net core3.1 application and deploy it. Then check if it works properly under this new site.
The site should be fine in the second steps, and replace it with the original_file. And the application also should be works fine.
The site can't work in the second steps, it means the environment in you server has some problem. It could be registry issue or ApplicationHost.config issue in IIS and so on. If it's very important for you, you can rasie a support ticket and let official engineer help you to figure out what happend in this windows Update
After the third step, if the new site can run the original_file file well. We can compare ApplicationHost.config between the new site and the original one to see if any settings have been changed.

IIS Web Platform Installer Error: 'doctype' is an unexpected token. The expected token is 'DOCTYPE'. Line 1, position 3

I've just created a new IIS website on a Windows Server 2008 in order to use it to deploy a new website.
The website is still empty.
If I try to open IIS Web Platform Installer under Management Tools, I get stuck on the error:
'doctype' is an unexpected token. The expected token is 'DOCTYPE'.
Line 1, position 3.
After closing the error, the Web platform Installer closes.
Do anyone know how to solve it?
Let me know in the comments if you need any other info or technical data, I have really no idea on how can I troubleshoot this
I had the same issue. However, I cannot uninstall IIS completely as I have many sites on my IIS running.
What I did was, I tried to install an IIS module which was not there. for eg, I chose CORS module.
You can get it from here https://www.iis.net/downloads/microsoft/iis-cors-module
Once I tried installing, WPI automatically uninstalled and reinstalled during the process and it resolved the issue.
Hope it helps!
As mentioned by #qbik Simply updating the Web platform installer fixed the issue. You can download the latest at this time from here.
Done, here's how I solved.
This issue seems to be strictly related to an old configuration of this server, so I had to manually reset it. If you face this issue, these following steps should work fine:
First of all, I had to remove the IIS role functionality from
Control Panel > Programs and Features > Turn Window Features on or
off > Roles.
Then, I restarted the server and added again the IIS role
functionality (make sure to check all of the asp net
functionalities).
After that, I restarted the server (again) and I have reinstalled: 1) DotNetCore.2.0.7-WindowsHosting (you've got to find the installer online, make sure to download the last version. 2.0.7 was the last when I made this question so on 25/05/2018) 2) Web platform Installer from here.
Executing web platform installer from all program inside start menu worked fine.
Hope it will be helpful
(See Also:
How to Install Web Platform Installer and Web Deployment)

This app failed to launch because of an issue with its license

I'm happily in the middle of coding then I try to launch my app in debug mode but I get this error message.
Unable to activate Windows Store app
This app failed to launch because of an issue with its license
The app was launching fine a few minutes earlier so this came as a surprise. I tried restarting Visual Studio but doing so did not help.
I got the annoying "renew your developer license" dialog yesterday I think. It had renewed without issue.
How do I make this error message go away so i can debug my app?
Well, I got it working by deleting the main project's 'bin' and 'obj' folders. Cleaning and Rebuilding wasn't enough. Hope this answer saves someone else the few minutes of confusion I just experienced.
I recently had a similar issue. In my case I had to uninstall the re-install the app to get it working.
Hope this helps someone. Also, to find out further detail about why it failed, you can checkout the event logs:
Event Viewer > Applications and Services logs > Microsoft > Windows > Aps > Microsoft-Windows-TWinUI/Operational
There might be some more detail in there. In my case it was logged as an error event which said the app could not be launched because of a temporary issue with its license.
I just uninstalled the existing version of the app from the start screen, and then launched the app again from Visual Studio and it is launched just fine.
I think the reason behind this is because of renewing the license of Visual Studio and trying to launch an app that was installed when the previous license was active.
I see doing stuff with the bin and obj folders appears to be the accepted answer to this.
I fixed this issue by selecting the 'Uninstall and then re-install my package. All information about the application state is deleted.' check box under the Debug tab of the project properties. You can uncheck it once you've done it once for all future builds.
I haven't had any issue with this solution. Simple fix and you don't have to worry about someone doing something to folders that could cause bigger issues.
http://daxdude.blogspot.com/2013/04/c-error-unable-to-activate-windows.html
I've had this issue a few times now, most of the time deleting the Bin and Obj folders will clear the issue up (These folders are automatically generated during a project build so don't worry about deleting them)
I have found whilst debugging on a remote device (A tablet or phone) that Deleting these folders doesn't solve the problem though - in this case the best solution I have found is just to do a restart on the device I was remote debugging to.
Simple but it works!
I just cleaned my solution and re-started Visual Studio. That did the trick for me - and didn't involve hunting around for files to delete, so you might want to try that first.
go to BUILD-->Clean Solution and click and after its has been cleaned again go to BUILD-->Rebuild Solution. After it has successfully rebuilt your solution just deploy it(Ctrl+F5). This solved the problem for me.

IIS error when attempting to start WebMatrix

When I attempt to start WebMatrix, I get an alert saying "IIS Express could not be initialized. Please make sure that it is installed and configured correctly."
I've uninstalled and reinstalled both IIS Express and WebMatrix, with no change in this behavior. The advice I've been able to find on the net has been to assume ownership of the HKEY_CLASSES_ROOT\Microsoft.IIS.VersionManager registry key and replace all child object permissions with the permissions from that registry key. This didn't seem to help.
Looking in Event Viewer, I can see .net runtime exceptions whenever iisexpresstray.exe or webmatrix.exe try to launch:
System
Provider
[ Name] .NET Runtime
EventID 1026
[ Qualifiers] 0
Level 2
Task 0
Keywords 0x80000000000000
TimeCreated
[ SystemTime] 2012-09-29T21:28:02.000000000Z
EventRecordID 162768
Channel Application
Security
EventData
Application: iisexpresstray.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentNullException >Stack: at System.Runtime.InteropServices.Marshal.FinalReleaseComObject(System.Object) at Microsoft.Web.VersionManager.IisExpressVersion.Dispose(Boolean) at Microsoft.Web.VersionManager.IisVersion.Finalize()
I would greatly appreciate any help in diagnosing and fixing this issue. WebMatrix is going to be almost essential to a project I have coming up soon. Thanks!
For some reason, installing IIS 8 Express fixed the problem.
Just wanted to note that I too had this problem. Based on a previous suggestion, I downloaded IIS 8 Express. It did not install but gave me a chance to repair (so I assume WebMatrix installed it). I selected the repair button and restarted WebMatrix. I am no longer getting the aforementioned error.

Debugger can't connect when starting local azure project

Ok, first of; here's what I did:
Install AZURE tools
Reboot
Start Visual Studio - new Azure project
Add web role (asp.net MVC 4 beta web role)
Hit F5 (debug)
It starts up the storage emulator and the compute emulator and starts to load in runtimes, and then I get a popup saying that the debugger couldn't connect.
Then after some googeling I'm suggested to try to run the application without running the debugger to see if I can acces the application. When I do I get this:
So I figure that IIS does not have permissions to access some file/directory. So I go to IIS and look up the application pool running the app, and it tells me that the identity in use is NetworkService, then I go give NetworkService full permissions to the entirety of the folder IIS has set for the application (which also happens to be the path to the project dir). Still I get the same error. Now I'm more or less out of ideas, but I try one last thing, which is to also give IUSR full permissions to the same dir, but this did not help either.
How can I go about resolving this problem? I haven't tried actually launching my project to Azure yet, cause if I can't even get it to work in development I don't see much point. Any and all help would be appreciated.
I ran into the same error today after uninstalling .NET 4.5/Visual Studio 11 Dev Preview, then installing ASP.NET MVC 4 Beta (this is before Feb 29th when the updated VS 2011 Preview drops).
Since I uninstalled .net 4.5, you just need to do an "aspnet_regiis -i" to ensure the .net framework (4.0) is set up with IIS 7.x this worked for me.
Edit: This will work if you uninstall/then manually install Visual Studio 2012 RTM as well.
I had a similar error yesterday. For me the problem was that the output of the build was empty in the target folder.
I tried to answer a similar question https://stackoverflow.com/a/9411422/182371:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log
file for the error messages. Mode details at
https://stackoverflow.com/a/8432621/182371
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0', right
click --> Explore.... Make sure that this folder is not empty and
contains all the files required to start a web project successfully.
As for the Access Denied error:
it could be just an IIS default setting to disable browsing. To resolve that, just navigate to that web site in IIS, find Directory Browsing icon, and press Enable. You will at least see the files inside that directory.
Also try not only 127.0.0.1:81, buta specific document inside that folder, like 127.0.0.1:81/Default.aspx
Take into account the fact that there's sometimes some mess with the ports. You see that in the error message it's port 82, but in your browser it's port 81. So make sure you're using the right port. Or, even better, in your service definition try to use some non-standard port for this to avoid remapping.
I've met the same issue. In the end, I had to reinstall IIS 7.
I got this exact same error and tried a re-install of IIS and the Azure SDK - nothing worked.
Eventually tracked it down to the "IIS URL Rewrite Module 2". I went to the Control Panel and chose Repair and it resolved it. If you have a section in your web.config then this might be the cause.
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk when upgraded from 2011.

Resources