Can I extend this time out...? If so.. is it a bad idea..? I have a report\nthat I'm running that is exceeding this timeout, I know.. optimize the\nreport,\nit's not under my control, else I would.. I would like to setup a virtual\ndirectory with a\nlarge timeout to run all my reports in... What process is in charge of\nmonitoring and recycling\n[aspnet_wp]..?\n\nOK.. I found out that yes I can override this in a configuration file...\nmachine.config\n<processModel\nresponseRestartDeadlockInterval="00:09:00"\nresponseDeadlockInterval="00:03:00" /> <!-\- = 180 sec -\->\n\nThis config setting I believe is inherited, don't know for sure... so now my\nquestion becomes can I\noverride this in web.config....??? I'll probably have already answered that\nquestion myself, but I would still like to know\nif I could do something like this in my web.config if not, why.....\n\n<processModel responseDeadlockInterval="00:10:00"/>\n\n\naspnet_wp.exe (PID: 1272) was recycled because it was suspected to be in a\ndeadlocked state. It did not send any responses for pending requests in the\nlast 180 seconds.