Hello, I am experiencing a rather peculiar problem. Currently we have two load balanced Win2K servers in production serving an ASP.net site. The SSL session terminates at the Load balancer as the server certificate is installed on it. Recently we have tried to replace one of the servers with a brand new Windows 2003 box. We have tested the web site in isolation on the new box and everything works fine. Now, the problems occur when we put the new server into the F5 pool. This is done by a simple status page which has a simple piece of text that we change to Online or Offline whenever we want the server out or in the pool. When the new server is put in and the server it is replacing is put Offline we get strange session behaviour. When we try to logon to the site and if it goes to the other live server we have not replaced then everything looks ok. As soon as the F5 round robins to the new server we get an accessed denied error. Looking at the code this occurs if the session state is null. Now we are using persisting session data to Sql Server rather than in proc. The web.config is pointing to the correct db server. I have checked the IIS application ID's are identical to the other server on the farm as this is used by the ASP.net sql session state tables. The validation key are the same. I have also checked the IIS settings and they all look OK. What could possibly be the problem? One other strange behaviour i have noticed is when the new server is put in the f5 pool and a user logs in the about page which it redirects to is missing a user control at the top which contains the menu!!!. Has anyone had these type of problems with Sql state with a mix of 2000 and 2003 servers? Regards Romeel
