asp.net unhandled exception

Question

I have an application that has been running in produciton for a while now, and every now and then it throws an akward exception that I catch in the global.asax session error event. This procedure sends an email out with the error message, source, and stack of the error, and that is usually sufficient information for us to find the problem. However, this particular error does not have the entire stack. It apparently dies before it gets to my application in the stack.

Below is the information that is sent to me in an email. Through some other logging within my application, I can find which page it is occuring, but without the stack showing any of my application's code, I really don't know where to start. Any help here would be greatly appreciated.

Error Info:

Message: Object reference not set to an instance of an object.

Source: System.Web

Stack:

at System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument)

at System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)

at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)

at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Interesting indeed! If you know which page it's on, can you examine the event handlers of any image buttons you have on that page? — n8wrl
– n8wrl, Commented May 29, 2009 at 19:02

Andomar · Accepted Answer · 2009-05-29 19:01:35Z

1

Are there any complaining users?

Wouldn't bother otherwise-- this might be triggered by a robot browser, or a user cancelling his request at an unexpected point, and many other reasons.

answered May 29, 2009 at 19:01

Andomar

239k55 gold badges387 silver badges412 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

fizch Over a year ago

This should not be robot. There is a user that is logged when this is happening. The users that would be complaining are our customers. We do not want them to complain, and we do not want them to see error screens.

Andomar Over a year ago

We had a similiar issue a couple of years ago. I talked to many users about it, and they all said they had never seen the error screen. So not every thrown error ends up as an error message in a user's browser. (Yours might be, of course.)

fizch Over a year ago

I have actually looked in the IIS logs to see if the error page was loaded and found that there were hits on it when this error message was sent.

Mitchel Sellers · Accepted Answer · 2009-05-29 19:02:21Z

0

I would start looking at the page that threw the error, then look at the various image button controls that you have. My guess would be a dynamically loaded control, that was not reloaded.

We can't say much until we see the code

answered May 29, 2009 at 19:02

Mitchel Sellers

63.3k15 gold badges115 silver badges174 bronze badges

3 Comments

mxmissile Over a year ago

I think that is the problem, he does not know which page is throwing the exception.

Mitchel Sellers Over a year ago

@mxmissile - he noted in the post that he can find the page in question.

fizch Over a year ago

this is hard to pin down. the problem is happening on multiple pages that are structured quite a bit different. it would appear that they all have dynamic data though.

Collectives™ on Stack Overflow

asp.net unhandled exception

2 Answers 2

3 Comments

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related