Action Canceled Message!

[e name]

Hello,

I am getting "Action Cancelled" message on an asp page which is running a
process that takes more then 25 minutes.
I have "Friendly error message" turned off on browser setting. And what
happens is this process processes a huge xml file
size of 4mb which is passed to the com object located on Application Server
as xmlElement from asp page on Webserver.

The process finishes successfully after 29 min but try to re run by itself
second time. I tried executing the same process
with same file from Application Server and it just executed it only once. so
I think their is some relation between
process being executed time due to some refresh or some setting in IIS
Website or IIS Application Pool or C:\WINDOWS\system32\inetsrv\MetaBase.xml
which causes the asp page to get a Action cancelled message right after
15-18min approx and at the same time issue an command to execute the process
again.

Their is no META refresh or timer on the page or in process I had verified
everything.

Please let me know if their is a setting that I can set in IIS Website, IIS
Application pool or in C:\WINDOWS\system32\inetsrv\MetaBase.xml to avoid
getting the message "Action Canceled" as well as not allow the IIS to
resubmit the process
execution by itself.

Please NOTE: If the file size is small of say 3MB everthing works ok on IIS
side to and does not resubmits as well don't get the "Action canceled"
cause the process is finished before 15 minutes and I also had set
scripttimeout on asp page.

Thanks in advance
HP

 

[Guest]

It isn't totally clear from your post what you are attempting to do here, but
one thing seems certain to me: You should not be trying to use an ASP.NET
page (which has a default timeout of 90 seconds) to do large-scale processing
that takes 29 minutes to run.

This is a candidate for a second process, one where your page deposits
something and finishes immediately, and the other process (Windows service,
executable, MSMQ, whatever) takes over and does the long-running task.

Even if you could get this to "work" - you run the risk of the vagaries of
IIS and its occasionaly habit of recycling the ASP.NET Worker process -
something that it can do at anytime, whenever it "feels like it".
Peter

 

[John Timney \(MVP\)]

I have to agree with Peter here, theres no way you can have a scalable web
application that takes 30 minutes to execute a single request - your going
to run out of working memory very quickly with multiple users. Use asp.net
to stick your request in a database (some form of queue) and create
something that can process the this without IIS being involved like a
windows service.

Regards

John Timney (MVP)

 

[e name]

Thanks for the suggestion. I guess I have no choice then to use windows
service due to this error.
I would have always preferred windows service for such task as we do use it
for other processes
but in this case it unsual. But any how we have decided to have both choice
for user.

Regards
HP