Recent projects to add a x86 compiled DLL,
First add reference, compile, error:
The first judgment is that the project can not add x86 references, so all the projects are compiled in accordance with x86, and corresponding to the application pool of IIS, also modified to enable 32-bit.
I thought I could display it smoothly, but it was an error. The error is the native development environment, but the deployment to the server test can be displayed normally.
View the application log in the system log according to the online prompts,
Based on this error message, online search, finally found a solution.
1. If the error is rewrite.dll, fix the corresponding IIS URL rewrite Module 2 in program-app and management.
2. If the error is aspnetcore.dll, fix Microsoft. NET Core 1.0.0-vs Tooling in program-app and management ...
Before I found the solution, I uninstalled all of the. Netcore programs and then re-pressed the. Net Core SDK to remain invalid, and finally, based on the methods in the scenario, searched for the
Dotnetcore.1.0.1-vs2015tools.preview2.0.3.exe, reinstall Repair.
It seems to be necessary to fix it once. And that is the error caused by the WINDOWS10 anniversary update, and finally understand why the server deployment can be normal.
Installing the recently released Anniversary Update (version 1607) of Windows seems to destabilize IIS by shutting down Application pools, thus resulting in a 503 error while trying to run an application, which was caused by some DLLs failing To load when the worker process starts. Fortunately, the lovely folks of the interwebz is coming to the rescue!
First, check out the Windows Event Viewer (win+x, V) to see what need to Fix:open "Windows Logs" and then "application" "Error" level entries with the source "IIS-W3SVC-WP" (could be different if the name of your IIS instance t the default one). In the details, you'll see a short message, like this:
The
Module DLL <path-to-DLL> failed to load. The data is the error.
Depending on your configuration, there may is different DLLs causing this kind of problem and they would occur one by one, So you'll need to keep checking the Event Logs and fix the issues until your application properly starts up. To be sure, before every attempt, stop IIS and close IIS Manager.
Here is the specific issues we ' ve experienced so far and what to fix them, but you could bump into completely different ones :
- "C:\WINDOWS\system32\inetsrv\rewrite.dll" (Reference)
- Go to "Programs and Features" (Win+x, F) and repair "IIS URL Rewrite Module 2".
- "C:\WINDOWS\system32\inetsrv\aspnetcore.dll" (Reference)
- Go to "Programs and Features" (Win+x, F) and repair Microsoft. NET Core 1.0.0-vs tooling ....
Happy updating!
Hi Paramesh,
I don ' t know from the top of my head, but you can try (re) installing them from PS using Web Platform Installer. Or If you have installed those from Web Platform Installer in the first place and then you probably still the. msi Insta Llers on your machine (for example on my machine they is under "C:\Users\Benedek\AppData\Local\Microsoft\Web Platform Ins Taller\installers ")-In this case you can repair them from PS using ' msiexec ' with the ' FA ' switch (which runs a forced R Epair).
This command works on my machine for URLs Rewrite 2, for the path might is different:
Msiexec/fa "C:\Users\Benedek\AppData\Local\Microsoft\Web Platform installer\installers\urlrewrite2\ 6a98b994adcc2e8d21507bf2b8baffb402c17395\rewrite_amd64.msi "
For "Microsoft. NET Core 1.0.0-vs Tooling", the installer (at least on my machine) are in one of the subfolders of " C:\ProgramData\Package Cache ", so for example the latest version I had installed (differs from what's in the blogpost) is "C:\ProgramData\Package cache\{da280276-4f5b-4918-8d40-20ca56dfa535}\ Dotnetcore.1.0.1-vs2015tools.preview2.0.3.exe ". "msiexec" won ' t is able to handle this, since it's an EXE, but you might is able to just run it from PS, although I ' m not Sure if that ' ll work without GUI.
Please let me know if it helped and if they work, then I'll add them to the blogpost.
Https://orcharddojo.net/blog/troubleshooting-iis-apppool-crashes-status-503-after-windows-10-anniversary-update
The Web project added x86 DLL reference, and the module DLL C:\WINDOWS\system32\inetsrv\aspnetcore.dll failed to load.