Diagnosing ASP_0147 errors

[CB]

Does anyone know of a resource for diagnosing ASP_0147 errors that appear
occasionally in server logs? They hit my server in bunches, on rare
occasions, for about an hour at a time.

Any advice appreciated.

[dNagel]

http://www.experts-exchange.com/Web/..._21183180.html
Internet Information Server: ASP_0147|500_Server Error

Might not be all that much help, but... hey, it was free... Make sure you
scroll past the nag screen ads to see the answers...

D.

CB wrote:

Does anyone know of a resource for diagnosing ASP_0147 errors that appear
occasionally in server logs? They hit my server in bunches, on rare
occasions, for about an hour at a time.

Any advice appreciated.

[CB]

I noticed that interaction before, and I don't think my situation is the
same, unfortunately. The problem with this type of error seems to be -- it
could have lots of causes, and there is no way to diagnose.

My system has no observable symptoms except that the application in question
slows to a crawl, and the 0147 errors appear in the logs.

[Bob Barrows [MVP]]

CB wrote:

Does anyone know of a resource for diagnosing ASP_0147 errors that
appear occasionally in server logs? They hit my server in bunches,
on rare occasions, for about an hour at a time.

Any advice appreciated.

The only aspfaq article mentioning this error that I can find is this one:
http://www.aspfaq.com/show.asp?id=2109

Does it help? Especially the part about enabling detailed messages on the
server ...?
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[CB]

I didn't do anything with error messages, because it's a production system
and I wouldn't want users seeing complex error messages; and also I am not
sure anyone is really seeing error screens. Users are definitely seeing the
system hang up and take 45 seconds to process a page. I personally have
never seen an error screen associated with this problem. It's difficult to
reproduce, alas.

My server logs include sections like this, usually following a gap of 30-90
seconds with no log entries:

2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp - 200
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500
2006-04-18 20:15:38 65.90.32.22 - 64.92.223.220 80 POST /survey.asp
|-|ASP_0147|500_Server_Error 500

That's nine entries from the same client in the same second, one of which
looks successful and eight being errors. The client is not really making
nine requests in one second. Maybe the user is getting impatient and hitting
submit repeatedly (since the server usually responds in a second or two), and
all the requests are being logged at the same time after the server gets
itself un-hung.

My challenge is to find out why it's hanging up.

[Bob Barrows [MVP]]

CB wrote:

I didn't do anything with error messages, because it's a production
system and I wouldn't want users seeing complex error messages; and
also I am not sure anyone is really seeing error screens. Users are
definitely seeing the system hang up and take 45 seconds to process a
page. I personally have never seen an error screen associated with
this problem. It's difficult to reproduce, alas.

My server logs include sections like this, usually following a gap of
30-90 seconds with no log entries:

I'm thinking that the setting for detailed errors at the server level may
help you with this. Otherwise, you should attack your code, putting more
error handlers in which log errors as they occur instead of sending detailed
messages to the client. Something like this:
http://support.microsoft.com/kb/299986/EN-US/

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"