Ah, OK.
InProc means it's stored inside the same process as the Web application. This is memory only, so when the process is restarted, you loose all your session variables.
The same applies to StateServer. This is a separate Windows Service that runs as a background process on Windows. Session state is stored (in memory) inside the process of this state server. Since the State Server process is not related to IIS / your Web application, it's much less likely this server needs to be restarted (on a reboot, but that's about it). That allows for a more reliable and scalable session state solution, as multiple web servers can access the same state server.
Not sure about the permission issues you may run into, though. The state server uses a custom TCP/IP port number, so that port needs to be open.
Look at the MSDN site for more info on the different type of state servers....
http://msdn.microsoft.com/library/de...sp12282000.asp
(A bit outdated, but the general ideas still apply)
Cheers,
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
