We have a couple of ARR servers and while configuring, troubleshooting, etc.. we kept one of the servers off. We turned it on and it started failing with the following errors getting logged in the event log.
Application Log
Source: Application Error
Event ID: 1000
Faulting application name: w3wp.exe, version: 8.0.9200.16384, time stamp: 0x50108835
Faulting module name: requestRouter.dll, version: 7.1.1952.0, time stamp: 0x5552511b
Exception code: 0xc0000005
Fault offset: 0x000000000000f2dd
Faulting process id: 0x8bc
Faulting application start time: 0x01d0b89d5edc49ba
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Program Files\IIS\Application Request Routing\requestRouter.dll
Report Id: 9caa10cb-2490-11e5-943b-005056010c6a
Faulting package full name:
Faulting package-relative application ID:
System log
Source: WAS
Event ID: 5009
A process serving application pool 'stark.dev.com' terminated unexpectedly. The process id was '52'. The process exit code was '0xff'.
Source: WAS
Event ID: 5011
A process serving application pool 'stark.dev.com' suffered a fatal communication error with the Windows Process Activation Service. The process id was '2792'. The data field contains the error number.
Source: WAS
Event ID: 5002
Application pool 'stark.dev.com' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
This last one was due to rapid fail being enabled in the app pool
The odd thing is that, Server 1 was working fine, but Server 2 wasn't. Odder still was that they were configured in the same way, at least it look that way, at first.
After a lot of troubleshooting, we found the issue in Server 2, which, surprise, surprise was not configured the same way as Server 1.
This is the offending rule:
We talked with Microsoft support who said that they were going to talk to the product team but I've not heard anything, so who knows.
No comments:
Post a Comment