IIS 7 and Above
IIS8 Application Initialization crashes the apppool
Last post Oct 12, 2017 03:09 AM by Yuk Ding
Oct 11, 2017 07:45 AM|R. Brink|LINK
I have a website (running in an ARR+NLB) environment. I have set the apppool to AlwaysRunning and on the website I set Preload enabled to "true".
So far so good. When I restart IIS on a webserver it auto starts the worker process. From what I've read IIS should also put an initial request on the MVC pipeline for the homepage "/" to preload the application, but this doesn't happen. We application gets
loaded successfully when I hit it with my browser the first time though. This seems strange to me. Anyone agree or am I wrong to assume the website should be hit by IIS itself to preload it?
So I dug a little deeper and found some settings to configure in Web.config. I added this to have IIS hit the Home controller's Index action to preload the website:
When I restart IIS, the apppool attempts to start up, but ends up crashing with crash reports in the Event Viewer:
Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: iiscore.dll, version: 10.0.14393.1532, time stamp: 0x5965b173
Exception code: 0xc0000005
Fault offset: 0x000000000002adff
Faulting process id: 0x1cd8
Faulting application start time: 0x01d34263ca26c9c7
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\inetsrv\iiscore.dll
Report Id: e5484169-2b3f-4755-8926-4e331787e78b
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 120820974363, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: 38d42d2c-bd5a-4433-a03c-7526c8a49465
Report Status: 0
Hashed bucket: b2c7269e2da3d04dfa31ee06a59fb78c
If anyone can shed some light on what I'm doing wrong here, I'd very much appreciate it!
Oct 11, 2017 09:56 PM|lextm|LINK
The version numbers indicate that you are using IIS 10. Why do you say IIS 8 in the title? Explain that and you might find the cause of the problem.
Oct 12, 2017 03:09 AM|Yuk Ding|LINK
It is a bit hard to get the root cause from the error message directly, so maybe you could just try to change the application initialization configuration one by one to figure out which setting is causing this issue.
I also find a document about the 0xc0000005 faulting module iiscore.dll could be caused by a extensionless module, maybe you could just modify the initial page to a URL with extension:
In addition, debug diagnostic tool could help you analyze the dump file: