Hello,
I'm running into a problem trying to get an application up and running on our production server, and I haven't been able to find anything relating to it, so I was hoping someone here might have a solution, or atleast point me in the right direction. I'm having a hard time figuring out the problem, because for some reason, it cannot be reproduced locally.
The application itself "runs", in so much as I can access the front page, and any other non-protected (against un-authorized access) pages. The problem comes once I login and attempt to access a page that makes use of session data. The session values that are expected to be there (that are explicitly set by the Login Action), are coming up as null every time. I can see in the trace that I am indeed getting an ASP.NET_SessionId cookie, and it appears to be the same value each time. But once a page that looks at the session, which is all of them, is attempted, the page crashes on a null reference exception. (For the sake of clarity, what's being stored are a pair of dates for a date range that is displayed on the master page.)
The major piece of confusion is that this problem does not ever occur locally - If i build and run local, everything works as planned. This makes testing for the problem a bit of a pain. The date range is correctly determined on Login if it was found to be null, and placed into Session before any of the pages load. There's never any lost Session problems locally. Only once the application is running up on the server. We're using the Windows Service Session State Manager to handle holding the Session, and other applications (non-MVC applications) running on the server are not encountering any Session issues. As far as I can tell, all the required components are installed for MVC. The application runs perfectly, with no errors, on my machine, and others. Nothing goes wrong until it's deployed to the server.
If anyone has any insight or advice into why this is happening it would be greatly appreciated