Thanks Cathi,

I'd already found it and had not had time to get back up here and let everyone know. It took a lot longer to find it since the help files make no reference to it when doing a search on deadlocks.

Jeff
>Hi Jeff,
>
>You can change responseDeadlockInterval in your machine.config file. It defaults to 3 minutes:
>
>

>responseDeadlockInterval="00:03:00
>

>
>>I have a application that is having the following problem.
>>
>>This app gives the heads of state around here access to their Accounts Payable info for a given period. It pulls the info from an as400 thur a datareader and then stuffs that info into a datatable in a dataset. Then depending on the users selected output type they can get this in several forms. All this works great with the exception of a few of these request can become rather large. Around 1 meg pdf is where the problem seems to starts. This size is a rare but it can happen and I still need to be able to handle this over our intranet. On these request I get the 'Server Application Unavailable' error page with an admin note saying I can find the problem in the system event log.
>>
>>Event Viewer Application Log Error Message:
>>aspnet_wp.exe (PID: 1944) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last 180 seconds. Yes I know 3 mins on the web is a long time but this is the way I have to do it for now and the vast majority of request will be handled in just a few seconds.
>>
>>I've looked everywhere I can think to see if I can adjust this time and can't seem to find it. It is not the scripttimeout setting.
>>
>>Any ideas?
>>
>>Jeff