S
Steve Bywaters
There are several hundred of my client's franchisees happily accessing my
ASP/VBscript web site... but one - just one - has reported the following:
"I have been trying to log onto the LSM since friday and get this message
when I want to go into any of the items on Home Page.
Response object error
'ASP 0156: '80004000'
Header error
/lsm/ListPolls.asp.Line 21
The HTTP header are already written to the client browser. Any HTTP header
modifications must be made before writing page content."
I have tried the page(s) in question and all is well... so have others - no
problem.
So how can ONE person get such a server-side error?
Points:
* She is using IE6 (.1) on W98
* I understand that the 'error' often is produced when a Redirect is issued
after starting to write the page... and that Response.Buffer will solve
that 'problem'. I have used this in the past, when *I* have seen an error
occur, but since she is the only one getting the error, and it (apparently)
happens on several pages), that would seem a silly way to go (since I do NOT
get the problem)
* Line 21 - as indicated the offending line - is ONLY called if
authorisation (via Session var) fails.... but she couldn't have got this far
into the site unless she *had* logged in, and auth. stored.... ???
Can someone provide more insight as to what's happening?
Steve
ASP/VBscript web site... but one - just one - has reported the following:
"I have been trying to log onto the LSM since friday and get this message
when I want to go into any of the items on Home Page.
Response object error
'ASP 0156: '80004000'
Header error
/lsm/ListPolls.asp.Line 21
The HTTP header are already written to the client browser. Any HTTP header
modifications must be made before writing page content."
I have tried the page(s) in question and all is well... so have others - no
problem.
So how can ONE person get such a server-side error?
Points:
* She is using IE6 (.1) on W98
* I understand that the 'error' often is produced when a Redirect is issued
after starting to write the page... and that Response.Buffer will solve
that 'problem'. I have used this in the past, when *I* have seen an error
occur, but since she is the only one getting the error, and it (apparently)
happens on several pages), that would seem a silly way to go (since I do NOT
get the problem)
* Line 21 - as indicated the offending line - is ONLY called if
authorisation (via Session var) fails.... but she couldn't have got this far
into the site unless she *had* logged in, and auth. stored.... ???
Can someone provide more insight as to what's happening?
Steve