oliverp101698
asked on
For TTom
Tom,
You answered one of my questions a while back but at the time I said that I may not be able to test the solution for a little while.
Well, I resolved the problem (it had to do with the Session collection and an old asp.dll) but can't find the question I asked anywhere. I assume it was removed for some reason.
In any case, you deserve your points so answer me and you will get them.
You answered one of my questions a while back but at the time I said that I may not be able to test the solution for a little while.
Well, I resolved the problem (it had to do with the Session collection and an old asp.dll) but can't find the question I asked anywhere. I assume it was removed for some reason.
In any case, you deserve your points so answer me and you will get them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Keep having to go deeper into the operating system!
Isn't it amazing (frightening) how complicated simple problems can be.
Tom
Isn't it amazing (frightening) how complicated simple problems can be.
Tom
ASKER
So true! But the learning experience makes it worthwhile in the end.
Oliver
Oliver
ASKER
I was trying to iterate over the session object but kept getting an error message that Contents was not a valid property.
Tom asked me what version of asp.dll was on our server. I found two versions: one old and one new. He suggested that I remove the old version of the file and see what happens. I was never able to do that because the file was always in use. After searching the MS Knowledge Base I was given the idea to look for all occurrences of the old asp.dll in the registry and replace them with the path to the new version. Lo and behold, about 10 registry entries were pointing at the old asp.dll. Pointing them to the new version solved the problem.
Oliver