Windows 8.1 / Windows 10 breaks my ASP.NET / IIS : "Service unavailable"

Url Rewrite-ModuleWindows 8.1

Url Rewrite-Module Problem Overview


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?

Url Rewrite-Module Solutions


Solution 1 - Url Rewrite-Module

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.

Solution 2 - Url Rewrite-Module

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

Solution 3 - Url Rewrite-Module

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

Solution 4 - Url Rewrite-Module

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

Solution 5 - Url Rewrite-Module

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

Solution 6 - Url Rewrite-Module

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.

Solution 7 - Url Rewrite-Module

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.

Solution 8 - Url Rewrite-Module

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.

Solution 9 - Url Rewrite-Module

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

Solution 10 - Url Rewrite-Module

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

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSimon_WeaverView Question on Stackoverflow
Solution 1 - Url Rewrite-ModuleSimon_WeaverView Answer on Stackoverflow
Solution 2 - Url Rewrite-ModuleGarDavisView Answer on Stackoverflow
Solution 3 - Url Rewrite-ModuleJimmy SohView Answer on Stackoverflow
Solution 4 - Url Rewrite-ModuleKevin DimeyView Answer on Stackoverflow
Solution 5 - Url Rewrite-ModuleChad CarischView Answer on Stackoverflow
Solution 6 - Url Rewrite-Module9Rune5View Answer on Stackoverflow
Solution 7 - Url Rewrite-ModuleDave MateerView Answer on Stackoverflow
Solution 8 - Url Rewrite-ModuleStuartView Answer on Stackoverflow
Solution 9 - Url Rewrite-ModuleMarco DuindamView Answer on Stackoverflow
Solution 10 - Url Rewrite-ModuleSteven ChouView Answer on Stackoverflow