>It would be nice if this could be application setting in the web.config. Some apps I would like to have a really short deadlock setting.
Have you tried that? Most of the config settings are hierarchical and you can set the values in the local files as long as you maintain the full hierarchy of nodes.
+++ Rick ---
>
>>Try editing the machine.config file on the web server. Look for the
section and increase the responseDeadlockInterval setting (it defaults to 3 minutes), for example:
>>
>>responseDeadlockInterval="01:00:00"
>>
>>You'll need to re-edit the file each time you install a new version of the .NET framework.
>>
>>
>>
>>>An ASP.NET page calls a method on an COM EXE. The request is a report that should take about 20 minutes to finish. In the web.config I've upped the executionTimeOut to 1 hour (as below).
>>>
>>>>>> <httpRuntime
>>> maxRequestLength="4096"
>>> executionTimeout="3600"
>>> />
>>>
>>>
>>>The ASP.NET page still times out after 3 minutes with the error message below. Any idea why the timeout is still happening?
>>>
>>>***
>>>Server Application Unavailable
>>>The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
>>>
>>>Administrator Note: An error message detailing the cause of this specific request failure can be found in the system event log of the web server. Please review this log entry to discover what caused this error to occur.
>>>****
