IIS resets my session variables [RESOLVED]

Environment:

Windows 2003 SP1, IIS 6, .NET 1.1

Every once in a while, my session variables will get cleared and I couldn't view pages which depended upon session variable values. Obviously.

I thought this was a minor problem and set the session timeout to 60 minutes. Still, they would get cleared out inexplicably. Sometimes after 20 minutes, sometimes almost immediately.


I checked the event logs, and this is what I found:

Quote:

---

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 6/1/2005
Time: 4:28:19 PM
User: N/A
Computer: MENDHAK
Description:
A process serving application pool 'DefaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '3264'. The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8007006d

---

The link did not help at all.

As far as I understand, the App pool is crashing, and W3SVC seems to be restarting as a result of this. And this is as far as I got.

Tell me what to do next, or if you know the solution, please post! :afrog:

I've never seen that error before. Check here:
http://www.kbalertz.com/kb_885654.aspx
"This issue may occur if the NT AUTHORITY\NETWORK SERVICE account does not have the permissions to the required registry keys."

I'd imagine that could be any permission issue.

But regardless - you should check that something isn't getting widely out of control in your code as well which may cause a recycle of the aspnet worker process.

I know that isn't useful but that's my best answer.

Thanks for taking the time out :)

Thing is, it's a very simple application. This is a prototype application I've made, so it's got very little code. The only code that I use is something like displaying the username (stored in a session variable). Other than that, it's entirely response.redirects to display the flow of the pages.

Nevertheless, I'll go through the code once to see if I do have something that might be causing this. An infinite loop perhaps?

I was googling a bit yesterday, when a few users mentioned that they were able to resolve this issue by running IIS 6 in "IIS 5.0 mode"

I'd like to try this and see if it helps. How can I set IIS to IIS 5.0 mode?

Found it in the metabase.xml file. To set IsolationMode, IIS5IsolationMode = "TRUE"

Let's see what happens...

At the bottom of the event viewer window, you should two radio buttons: "Bytes" and "Words". Select "Words", and you should have a more ... readable error number in the textbox at the bottom

:)

Yes, this is what I got:

8007006d

I am not aware of how this is of any help to me.

If you haven't solved this... might I suggest a scenario that may be your problem, but if you're dead on with that error message... perhaps it isn't. In fact, this scenario is probably unlikely in that its a unique situation, but I'm posting it for any future inquiries on this subject.

One of our developers was losing session state now and again... well, as it turns out something in the app was writing some data to web app's bin directory. I always thought that the application never restarted unless web.config was changed... well, it turns out that the framework watches that entire folder. If anything in there changes, it will rebuild the application - resulting in a loss of session state between requests if the application wrote any data to that directory on a previous request(an xml file or what have you).

Like I said - this probably isn't your situation - but its a suggestion nonetheless.

Quote:

---

Originally Posted by mendhak

Yes, this is what I got:

8007006d

I am not aware of how this is of any help to me.

---

Google :rolleyes:

http://support.microsoft.com/default...b;en-us;885654

Google? What's that? :ehh:

Yes, I've seen that article, I should've mentioned. I followed those steps, but the problem did not go away.

However, I edited the metabase and have set it to IIS5Isolation mode (again, this isn't an important server, just need the prototype working).

Thanks to everybody for their time.