Much like a previous post i made when using Toolkit controls... now I am getting it just using ScriptManager and some PageMethod callbacks

Surely someone out there has gotten this error and might have some tips on what to do about it?

The problem is pretty intermittent, and when it does rear it's ugly head, it takes about 4-5 refreshes of the page to actually work... there is absolutely no rhyme or reason.... no code was changed from working to not working and back to working, just simple F5 page resfreshes....

For note: while i cannot seem to get rid of the error in IE, the page does work fine in Firefox



** Edit/Add 5 hours later **

Totally clearing the "Temporary Internet Files" got rid of the error in IE.....    which sucks because there is no way to program around this... I'm going to have to sit there, wait for a client to break the site, call us, and walk him through clearing his cache.........

MorningZ:

For note: while i cannot seem to get rid of the error in IE, the page does work fine in Firefox



** Edit/Add 5 hours later **

Totally clearing the "Temporary Internet Files" got rid of the error in IE.....    which sucks because there is no way to program around this... I'm going to have to sit there, wait for a client to break the site, call us, and walk him through clearing his cache.........

I have also seen this.  It never happens on my localhost development server (either the one in VS2005 or just through my regular IIS).  It only seems to happen on the production server.  It never happens in Firefox.  I completely cleared the cache in IE which got rid of the error for about 5 minutes, then it came back after going between two pages.  Grrrrr.

Steph 

I think I may have solved my issue -- I created a separate application pool for the app to run in.  I have been clicking around in IE without error so far.  You might try that.

Hmm good tip, but...

At the time of getting that error, it's always hitting an IP local to my workstation (Windows 2003 and IIS6) and is sharing an app pool with nothing else...

*perhaps* the new version of MSAjax address this Sys error... i'm crossing my fingers  :-)