I have an ASP.Net Web API application deployed via IIS. It is in Windows Authentication enable mode only because I want to detect Windows users who access the APIs.
For a few days the application will work fine but occasionally it will fail. When the application fails it will present the login prompt several times (minimum 3 times) when requesting the API. Instead of responding to credentials a "Service Unavailable" message is presented. At this point the site's application pool stops and an application event log message is created, e.g.:
Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x52157ba0
Faulting module name: clr.dll, version: 4.7.2117.0, time stamp: 0x59cf5105
Exception code: 0xc00000fd
Fault offset: 0x00451a8d
Faulting process id: 0xe10
Faulting application start time: 0x01d3a9f540d7b456
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 83502af2-15e8-11e8-80ee-005056b72cd8
Faulting package full name:
Faulting package-relative application ID:
Within my code there is no any debugging error or configuration error. What will be the problem for that and how handle it?
You are hitting a STATUS_STACK_OVERFLOW
. The problem is in your application code, which you did not post. You are calling something recursively with no exit criteria. Luckily the system has created a dump for you, you simply have to look into it and get your answer.