I'm using ELAMH with Atlas and the atlas control toolkit,

Now, I can't be sure, but it seems they don't work well together. I have some errors that I receive on my server but not on localhost, and while the cause maybe something in my application - I cannot debbug it. Atlas causes empty msgboxes to appear, and ELMAH doesn't go into action, as it does on other occasions.

So,

1. Is it really the problem, the fact I'm using both? If so, how do I fix it, and still manage to use them?
2. If not, I guess the problem is still Atlas, how do I debug this
3. If the answer for question 1 didn't do it, how do I make the application not cause msgboxes to appear on errors?

Thanks in advance for any ideas!

I keep getting that annoying pop up, and, not only does it seem to originate for more than one error, it prevents me from debugging my application!

I'm using ELMAH, and I have the ScriptManager in my Master page, with Script Manager Proxies on pages that need Altas/Ajax.

Is this a conflict with ELMAH? Is it something I did? I don't want to turn off site validation, it's security, and that's important.

Any ideas?

The ScriptManager handles all of the Ajax exceptions differently than the main application.  I don't think you can even catch them in the Application_Error event.  If anyone has found a way to do this, I would love to know!  I don't know how I could have an app in the wild without elmah.

 I just found this on the elmah google group.  I haven't tried it yet, but it looks like the answer!

http://groups.google.com/group/elmah/browse_thread/thread/6de9a7baeedf8eda/b24284d572adcf6c?lnk=gst&q=ajax&rnum=2#b24284d572adcf6c