G
Guest
I'm running a really long process from ASP.NET and need some help...
I am making a method call when the user presses a button from my webpage,
which goes into a database and parses a file. This process could exceed an
hour, so the user is expected to press the button to start the process and
minimize the IE window and do other work while the application is processing.
Anyway, after a certain period in time, the page becomes "Page could not be
displayed" and I need to figure out how to work around that. Is there a
setting in IIS or the web.config that can help me keep that page alive
instead of the "Page could not be displayed" webpage?
Is that possible? I know it may not lead to a good user experience but
that's how it has to be for now until we can revisit this issue later.
Thanks....
I am making a method call when the user presses a button from my webpage,
which goes into a database and parses a file. This process could exceed an
hour, so the user is expected to press the button to start the process and
minimize the IE window and do other work while the application is processing.
Anyway, after a certain period in time, the page becomes "Page could not be
displayed" and I need to figure out how to work around that. Is there a
setting in IIS or the web.config that can help me keep that page alive
instead of the "Page could not be displayed" webpage?
Is that possible? I know it may not lead to a good user experience but
that's how it has to be for now until we can revisit this issue later.
Thanks....