IIs on 2000 Professional Session Variables

  • Thread starter Thread starter henryavl
  • Start date Start date
H

henryavl

I recently had to reinstall windows 2000 professional due to a harddrive
crash, I downloaded all the newest updates, now I find that session
variables are not being kept from page to page as it had with older
software. If any one else has this problem with IIs 5.0, frontpage 2002
server
extentions I would appreciate a tip. What I have found out so far is that
the session variables used with asp 3.0 are going away in favor of dot.net
asp...This is a repost from another group, the server appears to be
configured correctly, and the application still works fine on the server it
is published on, the problem appears to be only on my development machine
after installing the sp4 update for windows 2000 Professional.
Thanks
Henry
 
Here are the error the event log shows??

Event Type: Information
Event Source: Active Server Pages
Event Category: None
Event ID: 4
Date: 1/14/2004
Time: 10:53:44 PM
User: N/A
Computer: PEGGYANN
Description:
Service stopped.

Event Type: Information
Event Source: Active Server Pages
Event Category: None
Event ID: 3
Date: 1/14/2004
Time: 10:53:42 PM
User: N/A
Computer: PEGGYANN
Description:
Service started.

Maybe

http://support.microsoft.com/default.aspx?scid=kb;en-us;306996

and

http://support.microsoft.com/default.aspx?scid=kb;EN-US;244465

Just do what they have backwards???
 
Active Server Pages do NOT run as a service. ASP is a series of COM components what you may recognize as dlls. If you look in the Internet Information Manager you will find the asp.dll which is used to intercept calls to the http server and grab out of what is sent to the client the ASP nomenclature <%%>. That is all ASP (asp.dll) does. It is like an ISAPI component.

The guy at IISFAQ I know somewhat. He is really very good in his field. It was he that got me to bone up on my IIS knowledge. And he says ASP is not a service either.

The issue here is what type of service are we talking about? It definitely is NOT a Windows Service. What it is is the COM protocol that is used to communicate. That is what has died. Now why? You'll notice that the NET Framework using an executable that runs when someone first accesses your aspx pages. That stays running for a while not sure how long if no more aspx pages are accessed.

All I can figure is the NET Framework and your basic IIS have hit a conflict. Like a result of the latest MDAC security update. At least it was that that killed my Framework in Windows 2000 Professional and which can also kill it in Windows XP. Watch out. The blaster updates and the MDAC security updates can kill the NET Framework and as I suspect ASP when the NET Framework is installed. I'd stay away from the MDAC security updates. IMHO.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top