Hi,

I turned on the SQLState and it works fine. (I had to remove the non-serializable items stored in the session though).

About storing the variables in the master page, it was quite simple. I created some variables in the master page and they were available in all the other pages. My guess is, these variables would also be stored in the application server memory and would cause a problem in the clustered environment....

I have stored some of the variables used by lot of other pages of my website on the master page. As we are migrating to a load balanced environment, I want to know if I need to move those variables to a different place to make them still available even if the requests sent a different web server every time.

Had similar problems when I stored these variables in the session object and had to turn on SQLState to make them available in...