Session works on one site but not the other on the same machines

2
votes

So here is the set up:

  • There are two virtual machines
  • Two different sites
  • Both sites appear on each VM
  • Both sites are load balanced
  • Both sites use session
  • Both sites are using the same session state sever
  • One works, the other does not

I have tried so many things to glean any useful info I can:

  • I made a test page that sets session with a date time and then writes it out. This showed me that session is being saved but once per machine as though it were "InProc".
  • Changing the session state to be saved on a different machine still didn't work
  • IIS is set up correctly because I swapped the site's host bindings and there was no difference.
  • Session works as expected on a different environment
  • The websites have the same file structure and root
  • The machine keys are the same

So what the hell is going on? Has anyone had anything like this before? Any suggestions because I'd try anything right now. This has been a problem for over a week!

Update: (as I try more things I'll put them here)

  • It is not cookies since I changed cookieless to true and it still didn't work
2
asp.netsessionsession-state
When you say it doesn't work, what do you mean? Does the page come up? Is the session state just not being retained? Is there an error message? – Jeffrey Kevin Pry
it acts like InProc session. Where it is stored successfully but it is once per server. So because I have two machines I have two different DateTimes stored under the same Session Key – BritishDeveloper

2 Answers

2
votes

In order for session state to work correctly the site id's in applicationsHost.config have to be the same across all the servers.

1
votes

See this answer to this question. Is the Application Path in the metabase exactly the same on each server?