This topic is locked

Error on page

9/19/2005 10:15:24 AM
ASPRunnerPro General questions
R
roller author

I am getting the following page error when I try to view more than the default number of records or go to the next page of records.
Line: 179
Char:4
Error 'document.forms.frmAdmin. TargetPageNumber' is null or not an object
Code 0
Could this be because in order to solve Response object error 'ASP 0156 : 80004005' I have added <% response.buffer=true %> to the top of the page. I did try to erase Response.Flush line but that didn't seem to help with Response object error 'ASP 0156 : 80004005' .

Sergey Kornilov admin 9/19/2005

Lets start from th beginning.
What was the first error message you have seen?
Full error message and code line that caused this error will be helpfull.

R
roller author 9/19/2005

Sorry I am not clear.
First I got Response object error 'ASP 0156 : 80004005' when I uploaded the site to my service provider. The site works fine on local machine.
From another post (I only thought there might be a realationship between the problems after I started this post, sorry), you suggested this was because the service provider was using NT and proposed removing Response.Flush line from _list.asp. I couldn't still couldn't get it to work.
Adding <% response.buffer=true %> to the top of each _list.asp page did work for me and stopped the Response object error 'ASP 0156 : 80004005' from appearing.
The new error is generated by/appears on the Web Browser and is not an ASP error so I am not sure where the code line would appear. I get it when I try to view more than the default number of records or try to go to the next page of records.
I do not get the error on the local server if I do not put <% response.buffer=true %> to the top of the _list.asp page. I can't try the page without the <% response.buffer=true %> on the service provider because it reverts back to the first error.
I hope this makes sense.

Sergey Kornilov admin 9/20/2005

Hi,
could you send me an URL where I can see this error?

R
roller author 9/20/2005

I was able to recreate the problem on local server so I was wrong to link the <% response.buffer=true %> line to the page error. I have been using FrontPage to modify the _list.asp pages and it appears that any editing or formattingusing FrontPage causes this error to occur when the page is uploaded to a server. That's today's theory anyway and the site is working.
Sorry for causing confusion.