help: State server not working with WWW service

[Daryl Gross]

We have 5 web servers in an intranet web farm with one of them configured
as the session state server (sessionState mode="StateServer"). When the
WWW service is started on the session state server, all web servers stop
working properly after about 15 minutes of use because user sessions cannot
be accessed . We can get around the problem by stopping the WWW service
on the session state server, but this defeats the purpose of having 5 servers
available for serving up web pages. Any ideas as to why this is happening?
We are running W2K/SQL2000.

[Daryl Gross]

"Daryl Gross" <daryl.gross@ps.net> wrote:
>
>We have 5 web servers in an intranet web farm with one of them configured
>as the session state server (sessionState mode="StateServer"). When the
>WWW service is started on the session state server, all web servers stop
>working properly after about 15 minutes of use because user sessions cannot
>be accessed . We can get around the problem by stopping the WWW service
>on the session state server, but this defeats the purpose of having 5 servers
>available for serving up web pages. Any ideas as to why this is happening?
> We are running W2K/SQL2000.

A team member found the problem and I thought I would answer my own posting
to help anyone else out there with the same problem. Basically on a web
farm the W3SVC instance number for the web site must be the same on all servers
in the farm. The following article from Microsoft explains it in detail:
http://support.microsoft.com/default...;EN-US;Q325056