By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,562 Members | 1,282 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,562 IT Pros & Developers. It's quick & easy.

handling Request Timed Out

P: n/a
Some of my users are receiving an error:

Server Error in '/' Application.
----------------------------------------------------------------------------
----

Request timed out.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Request timed out.]
I have written code to handle both a Page_OnError and Application_OnError
for tracking purposes. I am trying to receive email notification when a
user receives this error. I have a generic error page that all unhandleable
errors are redirected to, but I log every error. I really want to know when
this error is occurring to my users. No notification are sent and my users
see the ugly server error screen.

What am I missing out on?

TIA,

bill
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
to prevent infinite loops, every page request has a timeout (which you can
change in your web config, or on the local page - Server.ScriptTimeout). you
are hitting this timeout, and asp.net is killing the thread executing the
request (which is why the page doesn't catch the error).

-- bruce (sqlwork.com)
"William F. Robertson, Jr." <wf*********@kpmg.com> wrote in message
news:ua**************@TK2MSFTNGP11.phx.gbl...
Some of my users are receiving an error:

Server Error in '/' Application.
-------------------------------------------------------------------------- -- ----

Request timed out.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Request timed out.]
I have written code to handle both a Page_OnError and Application_OnError
for tracking purposes. I am trying to receive email notification when a
user receives this error. I have a generic error page that all unhandleable errors are redirected to, but I log every error. I really want to know when this error is occurring to my users. No notification are sent and my users see the ugly server error screen.

What am I missing out on?

TIA,

bill

Nov 18 '05 #2

P: n/a
There is nothing on the page that could be causing an infinite loop. The
Sql query that is running on that page could take a significant time. So I
understand why the Page_OnError isn't catching, but what about the
application_OnError in global.

I also tried wiring a static method to
System.AppDomain.CurrentDomain.UnhandledException event in application
start, but that doesn't seem to help catch the error either.

bill

"bruce barker" <no***********@safeco.com> wrote in message
news:eI****************@TK2MSFTNGP09.phx.gbl...
to prevent infinite loops, every page request has a timeout (which you can
change in your web config, or on the local page - Server.ScriptTimeout). you are hitting this timeout, and asp.net is killing the thread executing the
request (which is why the page doesn't catch the error).

-- bruce (sqlwork.com)
"William F. Robertson, Jr." <wf*********@kpmg.com> wrote in message
news:ua**************@TK2MSFTNGP11.phx.gbl...
Some of my users are receiving an error:

Server Error in '/' Application.


--------------------------------------------------------------------------
--
----

Request timed out.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

Source Error:

An unhandled exception was generated during the execution of the current

web
request. Information regarding the origin and location of the exception

can
be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Request timed out.]
I have written code to handle both a Page_OnError and Application_OnError for tracking purposes. I am trying to receive email notification when a
user receives this error. I have a generic error page that all

unhandleable
errors are redirected to, but I log every error. I really want to know

when
this error is occurring to my users. No notification are sent and my

users
see the ugly server error screen.

What am I missing out on?

TIA,

bill


Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.