Good day,

I am getting the following error on SOME of the PC's on my network when they access one of my ASP pages:
error '8002801d'
/Page.asp, line 5

Line 5 in my code is as follows:
Session("UID") = ""

As I said this works on some PC's but not all. Does anyone have any idea what would cause this and how to solve the problem. My server is Windows 2003 running IIS 6.0

Thanks

It will have nothing to do with the PC's themselves. ALL asp code is executed on the web server. It might have something to do with how the webserver deals with traffic coming from various locations.

what is on lines 1-4? Sometimes the line number provided in ASP is erroneous. Also, do you have any kind of load balancing in play? Do you see anything in the event logs of the web server when this occurs?

Did u ask uncle google "Error '8002801d'"

Lines 1-5:
<%@ LANGUAGE=VBScript %>
<%
'Response.Buffer = true
'Response.Clear
Session("UID") = ""

As you can see lines 2 and 3 are commented out.

myle, yes I have been searching for days on google no help.

Hmmmm... Kill that language directive. It shouldn't be needed and the error you're getting is complaining about a missing library. See what happens.

Alternately, trying putting up a page that has nothing but the language directive on it.

I'm not at all convinced that the call to Session() is the real error...

I have tried taking out the language directive and having nothing but:
<%Session("uid") = ""%>

And I still get the same error?

Alright, that's funky.

Can you run any ASP at all?

How about a simple:

<% Response.Write("sup mang?") %>

Yes I can run some ASP, the pages that have no Session variables seem to work fine.

What is also puzzling is that if I reboot the server everyone can access the pages again.

Very very strange. Problem say will exist first thin gon a Monday, reboot the server everyone can work. Users go home at night turning off their PC's. Then on Tuesday for instance they come in, reboot their machines, login and it doesn't work, reboot the server again and everyone can work. Very very strange.

And as I said before it is not every single user that has the problem. Very very weird.

Classic ASP stores sessions in memory so if you are having problems where the session works for a while and then stops working I would be looking at the server stats for memory usage...

It could be that your sever simply can't allocate space for the session information or something similar.

Do you actually need to reboot the server or can you simply restart IIS?

Just rebooting IIS does not work.
And the thing is while the page is not working on some users PC's it is working on others still, very strange.

So what is the difference between what the users on the PC's that work do and the users on the PC's that don't work do.

Do they restart their machines?

Do they click a log off button or just close their browsers?

If some work and some do not it is unlikely to be a problem with the server itself but more a coding issue somewhere. I would suspect there is something that is causing corruption of the user session and the user session is not properly expirying or something similar.

That is the part that confuses me. There are users that are doing the same thing. Shutting their PC's down at night, some of them have XP and some Win 7, when they boot up in the morning and log on again, some of those work and some of them do not. And all the PC's are up to date in terms of Windows Updates. That is what has me so stumped.

Some of the XP machines that were shut down and then rebooted and logged onto work and some don't and same goes for Win 7.

Stop looking at the "defective" machines themselves. It is not the client. It isn't. Absolutely ZERO asp code runs on the client.

Look at what IIS is doing with traffic from those machines instead...

How many IIS servers do you have? What kind of authentication are you using? Are they hitting identical url's? etc, etc.

The application only runs on one IIS server.
The suthentication is Basic Authentication
They are all accessing the identical URL as they all access the URL from the main Intranet web page which does work.
I can find nothing in the logs to indicate anything that may be the problem.

IIS still smells funny. Check with operations and make sure everything is patched up correctly? Did this start happening at a certain point or is this a first rollout?