I recently was forced into moving up the chain from having a web application targeting framework 2.0 to framework 3.5--my pc's hd crashed and i was presented by my company's desktop IT folks with Win7 instead of XP Pro--I was running reportviewer 2005 reports and couldn't edit them so I just took the plunge.
My previous environment was vwd2005 and am now using full blown vs2010 (as per Win7). The web site is running on 2 load balanced IIS 6 machines that use sql server 2000 for sessionState. I'm now seeing why it is a bad idea to be forced into such a situation without much ability to prepare for the fallout. Prior to migration to 3.5 the web application ran for the most part without problems--a necessary tweak here and there. Since then, I've gotten alot of errors on pages/controls that never had a problem previously and I am entirely at a loss as to what is going on with this application. That said, on to the problem.
I have several pages that are throwing errors. The errors do not always occurr and they seem to occurr at random times of day--and seemingly regardless of user load. When the error on a particular page does occurr, a user experiences the error, use the back button and will retry as many as 3 times before the page runs as intended as if nothing was wrong.
View Complete Post