Application_Error Invoked in Global.asax when ScriptManager is added

hello.

well, it's a little difficult to see what's going on...any chance of at least showing the error message and error stack you got on the application_error method?

I am not sure if the stack stace will really help. Basically it invokes Application_Error and it causes Unhandled Exception because I have the code in this event doing Server.GetLastError to send the error information to the developer. Since the error is caused by Atlas, there is no Server.GetLastError so it's null. Because it is null, it causes the error. See the picture.

Basically, Atlas should not call Application_Error, and for some reasons I do not know what causes Atlas to call that and what's the error caused by Atlas so I can fix and get Atlas working on this project. Thanks.

hello again.

well, that's really strange...i mean, whgen exceptions are propagated to the error event of the application, you should allways be able to get the exception by using the Server.getlasterror. are you sure about this? btw, any chance of getting a small demo page that illustrates this problem?

Hmm... I am sure about this. Not sure through what demo page you are talking about. I can just create a blank new page, add the ScriptManager, runs it and it would be just like that.

After all, may be seeing it is easier to understand. I recorded it andposted it here. I appreciate any help on this.

hello.

well, it looks like you're already getting a null exception before adding scriptmanager to the page (i've noticed that message on the ouput window). regarding the demo page, i was asking for a page that reproduces that problem (i've been usnig atlas for some time now and i haven't got any errors like those). can you build a new asp.net project with a simple master and a simple page that reproduces that problem? if you can, then send it to me and i'll try to take a look at it...

Hi there,

No, it doesn't happen when I create a new project. Anyway, I have figured out the problem. Thanks for trying to help me out all along. It turns out to me that my Error Collection code has a problem and once I fixed it, I got the email about the error and after I searched online, it turned out to be that I didn't configure the web.config for Atlas properly.

howdy...

glad you solved it...