Re: Cached Logon

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 12/23/04


Date: Thu, 23 Dec 2004 01:45:39 -0700


"Roland Hall" <nobody@nowhere> wrote in message
news:eF6YLEJ6EHA.2568@TK2MSFTNGP10.phx.gbl...
> "Ken Schaefer" wrote in message
> news:uChlX4I6EHA.1260@TK2MSFTNGP12.phx.gbl...
> :
> : "Roland Hall" <nobody@nowhere> wrote in message
> : news:OqNjkx%235EHA.3736@TK2MSFTNGP10.phx.gbl...
> : > "Ken Schaefer" wrote in message
> : > news:Oo7Cj695EHA.2608@TK2MSFTNGP10.phx.gbl...
> : > :
> :
> : > I provided the link at MSFT where I got the files. You can see for
> : > yourself
> : > there are no non-printable characters. Again, this is not my code.
> Also,
> : > I
> : > cannot reproduce the problem now that the server has been rebooted.
> : > You're
> : > also apparently excluding the other particulars.
> :
> : I just wanted to address the points you raised by using Basic /
Integrated
> : Authentication with IIS, and also with having to authenticate on the
> "first"
> : page versus subsequent pages, and about clearing the cache. None of
those
> : things should have anything to do with the issue you are seeing.
>
> I agree.
>
> : I was not
> : trying to "exclude the other particulars", but rather explain why I do
not
> : think some of the issues raised where not relevant.
>
> Ok, I misunderstood your comment.
>
> : I agree that the situation you are in is a bit odd.
>
> Well, I'm no longer in it but because I was, I do not feel comfortable it
> will not reoccur.
>
> : I'm struggling to think
> : of a reason why you might have been seeing the behaviour that you were.
As
> : Roger Abell has mentioned, perhaps the in-memory cached copy of the ASP
> page
> : was somehow corrupt. Rebooting the box would have completely cleared
that
> : cache.
>
> Thanks Ken. If I give the wrong password for sa will it cache that
response
> for the file? I wasn't sure of the password as I never use sa for
anything
> and knew it as not blank. After it failed, I set the password so I would
> know what it was, but it still failed. That's when I started testing.
> However, during all this, the other files never failed although I don't
> think I tried them with the bad password [if it was bad in the beginning].
> With that timeline, the file [StraightASP.asp] that was failing appears to
> have been cached and tied to that filename and after the password was
> correct, the other files worked because they were not in the cache. That
> would also make sense as to why renaming the file would then work but the
> old filename would not since that file was cached.
>
> I wonder if anyone can confirm that it caches the filename with the
> authentication and until released, refuses additional credentials. It
> doesn't sound like it is working by design. Sounds more like what Oracle
> calls a 'feature.' (O:=
>

Too funny Roland :-)
Since you have said/shown the connection string was just hard
wired into the page, whenever the page is hit that is what gets
used. Connection pooling etc. should all happen only if the
existing (if any) connection is correct for the connection string
specification (but, of course this is none to recycle as the auth
failed). If the cached copy did have invalid sa+pwd combination
that would tend to explain all you have stated as far as I can see.

-- 
Roger


Relevant Pages

  • Re: Cached Logon
    ... "Roland Hall" wrote in message ... and about clearing the cache. ... > authentication and until released, ... Since you have said/shown the connection string was just hard ...
    (microsoft.public.sqlserver.connect)
  • Re: Cached Logon
    ... "Roland Hall" wrote in message ... and about clearing the cache. ... > authentication and until released, ... Since you have said/shown the connection string was just hard ...
    (microsoft.public.sqlserver.server)
  • Re: Cached Logon
    ... "Roland Hall" wrote in message ... and about clearing the cache. ... > authentication and until released, ... Since you have said/shown the connection string was just hard ...
    (microsoft.public.win2000.networking)
  • Re: Cached Logon
    ... "Roland Hall" wrote in message ... and about clearing the cache. ... > authentication and until released, ... Since you have said/shown the connection string was just hard ...
    (microsoft.public.inetserver.iis)
  • Re: Cached Logon
    ... "Roland Hall" wrote in message ... and about clearing the cache. ... > authentication and until released, ... Since you have said/shown the connection string was just hard ...
    (microsoft.public.sqlserver.security)