View Full Version : ASP, Action canceled issue

08-05-2004, 01:34 AM
We have just recently launched a web based application from Window 2000 Server to Windows 2003 Server.

The entire website is coded with ASP (VBScript) and we have just noticed a strange behavior...

Whenever there is a large amount of data (a contact list with over 4500 contacts) delivered to the browser the browser displays an "Action Canceled" page. The thing thats strange is that we never had that problem before the migration and we don't have that problem when only small amounts of data are comming back.

It seems like it must be a setting somewhere in IIS 6 but I haven't found any info anywhere.

Any help would be appreciated!

edit, here's some more info:

We have set the AspBufferingLimit higher in Metabase.xml to overcome another error that occured if we sent 15,000 contacts to the screen.

All the setttings are set up correctly in IIS, all of our code works fine everywhere. With the exact same script and exact same data on Windows 2000 everything comes back just fine.

On IIS 6 we get the "Action Canceled" screen. We have traced the response with Ethereal (a great tool for tracking packets) and nothing comes back at all... the action was truely canceled.

Our new server is much better than the last server as far a specifications so I am confident it is not a server performance issue.

08-05-2004, 07:20 AM
Even if there's no problem with IIS6, I wouldn't display 4,000-15,000 contacts at once! :eek:

Why not do recordset paging (http://www.google.com/search?hl=en&ie=UTF-8&q=recordset+paging%2C+asp&btnG=Google+Search) and just display 10-20 contacts at a time?

08-07-2004, 12:09 AM
Our new system that will replace this one does utilize recordset paging.

This legacy system did not because we needed the ability for the user to "check all" and the programmer working on that part did not know how to keep track of all the contacts that were checked on each page as the user navigated through the recordset.

Regardless, this code worked on our other server fine, it stopped working when we migrated to IIS6.

Roy Sinclair
08-09-2004, 04:51 PM
Try adding a "response flush" call every hundred times through the loop as your page processes the input. If it's a timeout problem that'll let IIS know your page is still alive and active.