DB intensive app: ThreadAbortException

Hey all
I'm debuggin an internal tool that is able to display selected records and related data or generate an entire page consisting of all the records and related data.

After c. 2min a ThreadAbortException appears and I'm pretty much at my wit's end. ASP.net's global settings application timeout is set to 1000 as is the execution time in the script ( Server.ScriptTimeout = 1000; ) .
web.config compilation is set to debug (debug=true).

Even when removing everything but the querying code the page encounters the ThreadAbortException. It also makes using of the Wilson OR Mapper but I don't think it is the cause of the problem..

I turned the existing page into a Windows.Forms application and the page generated fine. (It's a 383Kb file - to give u an idea of the amount of data queried). However when ran as a web application it fails after c. 2min.

Any ideas would be appreciated..

In my opinion if a page takes longer than 5 seconds to generate, it took too long. (I've made exceptions for up to 10 seconds before in some instances.)

2 minutes is entirely too long. It doesn't belong as a web app. You need to have something in the back ground running this process. There are too many things that could case problems. What happens if the user closes their browser? What if they hit refresh in the middle of a load? What if they go to another page while loading? etc...

That being said, it's hard for us to debug something like that from here. A ThreadAbortException doesn't sound exactly like a timeout. It almost seems like there's something else going on. But without a lot more details, it would be difficult to know for sure.

In my opinion if a page takes longer than 5 seconds to generate, it took too long. (I've made exceptions for up to 10 seconds before in some instances.)

2 minutes is entirely too long. It doesn't belong as a web app. You need to have something in the back ground running this process. There are too many things that could case problems. What happens if the user closes their browser? What if they hit refresh in the middle of a load? What if they go to another page while loading? etc...

That being said, it's hard for us to debug something like that from here. A ThreadAbortException doesn't sound exactly like a timeout. It almost seems like there's something else going on. But without a lot more details, it would be difficult to know for sure.

I have copied the code from the server and debugged it with Visual Web Developer (Express) on my machine but the page generates just fine so it does not seem to be the code but rather server config or something related.

The page is an internal tool and something not frequently used. It compiles a lot of data into a readable format. It could be generated into a pdf or any other format but that would not save any significant amount of time.

I can understand that the info provided could be a little short but when an exception like this occurs in a situation such as this causes like scripts taking too long, et al are the first causes one thinks of.

The fact that it runs fine as a Windows.Forms app and from my machine would indicate it's a problem with the IIS config.

The fact that it runs fine as a Windows.Forms app and from my machine would indicate it's a problem with the IIS config.
Can you tell us anything about the IIS Config? Or is it possible that there is a firewall between the other server, and your data source? Again, we don't have access to check these kind of things...