email article printer friendly

Letters to the Editor

Letters to Visual Studio Magazine are welcome. Letters must include your name, address, and daytime phone number to be considered for publication. Letters might be edited for form, fit, and style. Please send them to Letters to the Editor, c/o Visual Studio Magazine, 2600 El Camino Real, Suite 300, San Mateo, CA 94403; fax them to 650-570-6307; or e-mail them to .

Posted December 16, 2003

Stop Losing Session State
We're running a Web farm and using SQL session state; we came across an issue where we were losing session state between servers. After much searching, I found the solution on Microsoft's Web site and wanted to share this important information that goes along with Leonard Lobel's ASP.NET column, "Manage Session State on the Server" [October 2003].

You need to check a couple things if you're losing your session state in a Web farm. Leonard describes one method in his article: You need to make sure you have a consistent machine key across all machines by modifying the "machine.config" file. We made this change in our "web.config" instead of the "machine.config." However, you should look at this next solution if you still have problems. This fix can be a little trickier, because it requires changing the IIS metabase. The problem is that the application path of the Web site "\LM\W3SVC\2" must be the same for all Web servers. If you add more Web sites to one server than the other and then you put them in a Web farm, your application instance ID will probably be different. The fix is fairly simple but requires that you change the IIS metabase and change the instance ID.

I recommend the Microsoft Knowledge Base article 325056 for detailed information on both of these problems and how to fix them.

I hope this information we found the hard way will help your readers.

Eric Renken, Niles, Mich.