I have done a quick scan over the newsgroups and didn't find any
postings about this so I thought I'd quickly post it and see if anyone
has had the same error or was aware of this.

We use Windows Server 2003 that hosts an ASP web site for our local
office intranet. One of our pages, that displays records from an
Access database, works fine if it is displaying only a minimal amount
of records (~50 to 100 sorry can't give exact numbers) but if the
number of records is large (we have tested with 1000) then we get the
HTTP Error 401.5 - which is a security error!

My apologies for not fully testing this before posting - but reducing
the number of records solved the problem so we didn't pursue it any
further. Anyway if you are experiencing the same problem may be it

HTTP error 401, sub-error 5, is an error that originates from an ASP page
that sends some 401. My guess is that on IIS6, the ASP output response
buffer is now capped at 4Mb by default (configurable), and it is that limit
which your large #-of-records page is triggering.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
I have done a quick scan over the newsgroups and didn't find any
postings about this so I thought I'd quickly post it and see if anyone
has had the same error or was aware of this.

We use Windows Server 2003 that hosts an ASP web site for our local
office intranet. One of our pages, that displays records from an
Access database, works fine if it is displaying only a minimal amount
of records (~50 to 100 sorry can't give exact numbers) but if the
number of records is large (we have tested with 1000) then we get the
HTTP Error 401.5 - which is a security error!

My apologies for not fully testing this before posting - but reducing
the number of records solved the problem so we didn't pursue it any
further. Anyway if you are experiencing the same problem may be it
will solve for you to.