Application not responding with state startedRSS

3 replies

Last post Jun 04, 2019 09:29 AM by Able

  • Application not responding with state started

    Jun 01, 2019 05:10 PM|Catarina3812|LINK

    We have an IIS instance with various applications with the same structure and configurations.

    We usually experiencie that some applications with State 'Started' doesnt respond to HTTP requests.

    Our Application pool configurations are like these:

    IIS config

    Anyone with similiar problem that can help us find the solution?

    Best regards

  • Re: Application not responding with state started

    Jun 01, 2019 11:03 PM|lextm|LINK

    Lex Li
    IIS Consulting Services at
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Re: Application not responding with state started

    Jun 03, 2019 11:42 AM|Catarina3812|LINK

    Thank you for your reply.

    We started some tests and you might think that is something about CPU application pool parameters.

    We have an Application in IIS 8.5 (WinServer 2012R2) with CPU following parameters:

    Limit (percent): 60

    Limit Action : KillW3wp

    Limit Interval(minutes): 1

    And in many cases our application stops responding and its state continues with “Started” (and there are no errors in Event viewer). With that we have to manually use “recycle” to restore it. It takes some time to restart and the following error is recorded in Event Viewer:

     A worker process 'XXXXXX' serving application pool 'XXXXXX' failed to stop a listener channel for protocol 'http' in the allotted time.  The data field contains the error number.”


    In the case of non responding app, if we manually “stop” the  application pool the error is:

    “0x80070425”. When we trigger the “start” the app starts running normaly.

    Should we change the "Limit Interval(minutes)" to a 5 min?

  • Re: Application not responding with state started

    Jun 04, 2019 09:29 AM|Able|LINK

    Hi Catarina3812,

    According to your description, I suggest that you could try below ways to solve the error:

    1.It is possible that your worker process is too busy to respond to the ping, so IIS tries to terminate it. When IIS tries to terminate the process, it fails, because the process is still hanging on to areas of memory.
    Go into IIS, click Application Pools, then right-click on your app pool and choose Advanced Settings. Under the Process Model heading, choose False next to Ping Enabled and see if that fixes the issue. Another option is to increase the Ping Maximum Response Time.

    2 I suggest that you could set application pool to enable 32-bit application pool as false.You could see as below:


    Best Regards


    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact