After installing iisnode on Windows Server 2008 SP2 (32 bit), all previously functioning apps report a "HTTP Error 503. The service is unavailable." None of these applications are registering or using the iisnode module.
The application pools are stopped after processing their first request.
The event log reports the error as EventID 5002 with:
"Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool."
Prior to that error, there are several Warnings as Event ID 3139 with:
"A listener channel for protocol 'http' in worker process '1688' serving application pool 'DefaultAppPool' reported a listener channel failure. The data field contains the error number."
I've given the app pool identity read/execute permissions to the node.exe (v0.8.14), as well as C:\Program Files\iisnode\iisnode.dll.
If I remove the iisnode module from iis, the sites and app pools run fine.
Any ideas on how to resolve these errors?
It is due to this bug: https://github.com/tjanczuk/iisnode/issues/231. The bug is already fixed and a new version of iisnode with the fix will be released shortly.
In the meantime you can use iisnode 0.2.0 on Windows Server 2008 R2 or move back to iisnode 0.1.21.
FYI for anybody getting this error in the Windows Event Viewer:
The Module DLL C:\Program Files\iisnode\iisnode.dll failed to load. The data is the error.
but not using Node, the solution for me was simply edit the C:\Windows\System32\inetsrv\config\applicationHost.config file and remove all lines referencing iisnode (there were 2).
Essentially we had synced an old IIS server to a newer one to migrate the code across, and the old server had IISNode installed, but the new one didn't. Since IISNode wasn't actually needed by the app, simply removing the references to it from the IIS config solved the problem for us.
Related
I am new to .Net core environment and facing issue while deploying application into IIS.
After publishing code and deploying into IIS server(Version 7), I am able to start application from Kestrel by going into directory where application hosted and running below command.
c:\inetpub\demoapp\dotnet "My App.dll"
By running above command, Kestrel is running on http://localhost:5000 and I am able to browse from browser. I am using latest .Net Core version 2.2.
But when I am trying to execute URL from IIS hosted application, I am getting below error.
HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure
Below is the event log from windows application log.
Application '/LM/W3SVC/49/ROOT/demoapp' with physical root 'C:\inetpub\demoapp\' failed to start process with commandline 'dotnet .\MyApp Web.dll' with multiple retries. The last try of listening port is '2405'. See previous warnings for details.
Anyone having idea how to resolve it?
In my case, It was win-64 architect issue.
You can change or switch architect from win-64 to win-86 then publish and don't forget to change Enable 32-bit Applications in IIS manager:
Right-click on the Application Pool and select “Advanced Settings…”
or select the same from the Actions pane after selecting the
Application pool.
Change the “Enable 32-bit Applications” to True (if you want the
application pool to spawn in a 32-bit mode)
Click OK.
p.s.: Don't forget to delete existing published files.
I install the URL Rewrite from the Web Platform Installer.
No added rule.
Then, when I access website url, it returned 503 code and Application Pool was stopped.
It works normally when I uninstall the URL rewrite module from Control Panel.
I have tried many searches on google but no results.
I found that in Event log:
- The Module DLL C:\Windows\system32\inetsrv\rewrite.dll failed to load. The data is the error. Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
(rewrite.dll is exits)
Any ideas?
In event log I found the same message. I.e. The Module DLL C:\Windows\system32\inetsrv\rewrite.dll failed to load. The data is the error.
For me the solution that worked was to replace the "rewrite.dll". In 2 of our other server it was working fine and they were installed in 2017. So I just copied the "rewrite.dll" from that server and replace it on my new server.
For me the older version(v7.1.1952.0) of the dll works, but new version ( v7.1.1993.2351), which comes with the latest setup, doesn't work.
BTW you need to stop the IIS before you replace the dll and start again.
I had the same experience and nothing I did fixed the issue e.g. repair, reinstall, restart, etc.
Then I removed what the Web Platform Installer installed and manually installed the x64 version of URL Rewrite and everything now works nicely.
Make sure what you’re installing matches the OS.
My team's Asp.net 5 web app (1.0.0-rc1-update1) is getting w3wp.exe crashes on IIS 7.5 (Windows Server 2008 R2) both when restarting IIS and intermittently during normal operation of two load balanced instances.
It seems to be the same error as in the following github issue. The error and fault info are nearly identical:
https://github.com/aspnet/IISIntegration/issues/35
'w3wp.exe' (Win32): Loaded 'C:\Windows\System32\apphelp.dll'. Symbols loaded.
The thread 0x6f54 has exited with code 0 (0x0).
Unhandled exception at 0x000000007717298A (ntdll.dll) in w3wp.exe: 0xC000070A: Status 0x (parameters: 0xFFFFFFFFC0000008, 0x00000000000002F8, 0x00000000003E59F0, 0x000000000038A280, 0x000007FEF4CF88F4).
Exception thrown at 0x000007FEF4CF88F4 in w3wp.exe: 0xC0000005: Access violation executing location 0x000007FEF4CF88F4.
Unhandled exception at 0x000007FEF4CF88F4 in w3wp.exe: 0xC0000005: Access violation executing location 0x000007FEF4CF88F4.
The program '[4540] w3wp.exe' has exited with code 0 (0x0).
This issue does not appear for us on IIS 8 with Windows 2012 R2. It seems to be an underlying HttpPlatformHandler or DNX stability issue with IIS 7.5 vs 8.
Are others seeing this problem? Has anyone seen an easier workaround for this issue than upgrading the windows/iis version? It does not seem to be deterministically triggered by our application code. The github issue has not been updated for some time and unfortunately we may not be equipped to do crash dump analysis or process debugging.
Re: HttpPlatform Log
I turned on the HttpPlatform log using the webconfig setting:
<httpPlatform processPath="..\approot\web.cmd" arguments="" stdoutLogEnabled="true" stdoutLogFile="..\logs\stdout.log" startupTimeLimit="3600"></httpPlatform>
The startup is logged as usual on initialization, but doesn't log an error when the crash is reproduced:
Hosting environment: XXXXXX
Now listening on: http://localhost:XXXX
Application started. Press Ctrl+C to shut down.
I had the same issue and it's coming from a bug in aspnetcore.dll (https://github.com/aspnet/AspNetCoreModule) occuring on a few given combination of Windows (7 for instance) & IIS (7.5 for instance). You can find this module somewhere in your c:\windows\systemXXX.
When I get the lastest from GitHub dev branch, it's fixed for me.
I believe the fix lies in the changelist: https://github.com/aspnet/AspNetCoreModule/pull/59
This version is not officially delivered yet and is not packaged in the 7.1.1971 version of the DLL which is the latest as of now.
After upgrading from Windows 7 Pro x64 to Windows 10 Pro x64, I cannot start IIS. Most of the Windows 10 system works fine. Some study tells me that the primary problem is that the Windows Process Activation Service (WAS) will not start.
I have another machine that upgraded to Windows 10 with IIS fine (Windows 7 Home Premium x64 up to Windows 10 Home Premium x64).
The IIS on that machine works OK (it only serves one website; so simpler setup.)
I have had NO LUCK finding anything on the Internet that resolves this.
I tried using the clean.iinstall IIS config files (no improvement).
I tried uninstalling IIS - uninstall failed and rolled back (see below).
I tried uninstalling WAS - uninstall failed, and rolled back.
DETAILS:
My first error trying to run IIS Manager program:
One or more problems have been detected during IIS upgrade. As a precaution,
one or more IIS services have been disabled. Please review the following error message:
Data loss has occurred - You upgraded your operating system or switched from one Windows SKU
to another SKU, and data from the previous installation of IIS has been lost or copied incorrectly.
As a result, the services W3SVC and MSFTPSVC have been disabled. Before enabling these services,
you should review the latest IIS 7.0 compatibility information.
(The link to see the IIS 7.0 compatibility information was a dead link.)
I decided to give it a try despite the compatibility warning. I started the services IIS, MSFTP, WAS and W3SVC (depends on WAS), then tried to start IIS Manager.
Failed to connect
There was an error when trying to connect. Do you want to retype your credentials and try again?
Details:
Creating an instance of the COM component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344}
from the IClassFactry failed due to the following error: 800700b7
Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7).
FACTS:
The IIS configuration files exist with non-zero length; they look coherent.
C:\Windows\System32\Inetsrv\Config
ApplicationHost.config
Administration.config
Redirection.config
I have a backup that I made that should be good (not just the automatic backups).
machine.config exists ok: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
The appPools folder exists: C:\inetpub\temp\appPools
The upgrade changed IIS from v7.5 to v10.0.10240.16384
This machine has one user account (me) and the account is marked Administrator.
My previous Windows 7 Pro with IIS 7.5 worked FINE for several years. IIS was giving no trouble before the upgrade.
I can use other network stuff OK: Internet, Outlook, PuTTY, MySQL Workbench (remote & local), and FileZilla.
Trying to start the Microsoft FTP service, or run appcmd or start W3SVC or WAS all give the same error:
Error 183: Cannot create a file when that file already exists.
appcmd list backup --> failed (running as Admin)
ERROR ( hresult:800700b7, message:Command execution failed.
Cannot create a file when that file already exists.)
Event Log after error starting WAS:
The configuration manager for Windows Process Activation Service (WAS) did not initialize.
The data field contains the error number.
error # = B7000780
I used the MS error lookup tool:
To see the appcmd error ( 800700b7)
for hex 0x800700b7 / decimal -2147024713 :
STIERR_HANDLEEXISTS stierr.h
1 matches found for "800700b7"
To see the WAS error (B7000780)
as an HRESULT: Severity: FAILURE (1), Facility: 0x1700, Code 0x780
for hex 0x780 / decimal 1920 :
SQL_1920_severity_10 sql_err
Skipping rebuild of index ID %d, which is on a read-only
filegroup.
ERROR_CANT_ACCESS_FILE winerror.h
The file can not be accessed by the system.
2 matches found for "b7000780"
I tried to uninstall IIS: 11/25
- uninstalled in windows features
- system did the work, I restarted system
- main system booted ok; then it treated the features
- the features uninstall failed at about 85% of total work
"We couldn't complete the features"
- system did a rollback
At reboot time, (some) services statuses are:
IIS runing auto IIS Admin Service (depends on HTTP service)
MSFTP off auto MS FTP Service (ftpsvc)
W3SVC off auto World Wide Web Publishing Service (depends on WAS)
WAS off auto Windows Process Activation Service
NetMsmqActivator off Auto Net.Msmq Listener Adapter
NetPipeActivator off Auto Net.Pipe Listener Adapter
NetTcpActivator off Auto Net.Tcp Listener Adapter
AppHostSvc off Auto Application Host Helper Service
==> THESE AUTO SERVICES ABOVE SHOULD BE RUNNING, BUT FAIL TO START PROBABLY DUE TO THE 'WAS' PROBLEM !
HTTP service is hidden, running:
sc queryex http ==> running
RPC and its dependencies are all OK, running.
I tried to uninstall WAS windows feature:
The system did the uninstall work, restarted, "could not complete features", rolled-back changes
I ran process monitor, but I could not see anything particular to resolve.
11/29 changed out the IIS configuration files, to use the clean.install versions:
C:\Windows\System32\inetsrv\config
I replaced applicationHost.config with applicationHost.config.clean.install (renamed it to the regular name)
I replaced administration.config with administration.config.clean.install (renamed it to the regular name)
I rebooted
I still could not start FTP or WAS, so maybe it's not getting far enough to read the configuration files?
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.