This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 59%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
We're facing a critical issue with our API server. It's built on C# .NET 4 with a C++ backend. The problem manifests as certain requests hitting the IIS of the backend server some instances, these requests remain stuck in the AuthenticateRequest state, which is at the very beginning of the IIS pipeline's request lifecycle. Most of them become stuck there and eventually time out.
Key points about our setup:
The implementation heavily utilizes asynchronous operations.
There are no database locks causing contention.
CPU load consistently remains at 10-20%, indicating no significant strain.
Our environment runs on Windows Server 2019 with IIS version 10.0.17763.1.
We operate two servers (server 1 and (server 2) connected to a single database, both running the same project. Additionally, we run identical APIs on both servers for synchronization purposes.
However, the issue only occurs on server 1; server 2 functions without problems.
We're open to any advice or ideas for further debugging on IIS, along with any additional information you may need.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 70%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYD%3C/text%3E%3C/svg%3E)
Hi @Parmeshwar Kale,
If the requests are consistently getting stuck in the AuthenticateRequest state, consider capturing a process dump of the IIS worker process (w3wp.exe) while the issue is occurring.
You can use PerfMon to collect data and DebugDiag for analysis. But analyzing the dump file is a complex process, so I recommend you to open a support ticket via: https://support.microsoft.com, there will be professional technicians to assist you in grabbing the dump file and analyzing it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
AuthenticateRequest is part or the asp.net pipeline. this event handler is typically defined in global.aspx (or its code behind) file. but any HttpModule could subscribe to the event (see web.config for list of HttpModules registered). you need to debug the code (maybe add trace events).