Closing ASP script bracket showing up on all pages 1

[riley3]

Hello,
I've got a minor problem with a web site using ASP & VBScript. I did a lot of testing on our web server and everything appeared to be ok. However, after installing it at the customer's location a %> ASP closing bracket shows up on every ASP page, always close to the top of the page. I've gone over the code many times thinking I had an extra closing bracket but could not find one. It looks just fine on my server, a clean page with no closing bracket. Their server is the same as our server, Win server 2003 & IIS6. I must have missed something in the initial setup in IIS but again; I've been over and over the settings and find the problem. Does anyone have any idea what might be causing the problem? Riley

 

[DotNetGnat]

so you mean to say %> appears on the top of the page and the remaining page works fine or are you saying that you just see %> on the top of every page...

-DNG

 

[riley3]

Yes, that's exactly how it's working. The page loads fine and the database processing on the page also works ok. In the top left corner of some pages the %> shows up and on the pages where a list of items is displayed the %> shows up just above where the list starts, not at the top like on the Home page. Thanks for you quick response.
Riley

 

[Turkbear]

Hi,
That usually means an 'extra' <% is on the page ( with no matching %> ) ..Try counting them - like with ( ) s - or, if your text editor allows it, check for unbalanced ones..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[riley3]

I agree that it sounds like there is an unmatching %> bracket. There are about 20 pages and they all worked fine while running on my server. After installing the same pages on the customer's server the %> bracket started showing up on every ASP page. I've counted them (brackets) several times and it's unlikey I would have made the same error on every ASP page. (where have I heard that before ) Some of the pages are a short database update routing with very little ASP code ( maybe 15 lines) and no HTML code on the page so it's easy to count. That's what made me think it was something I did in IIS. Thanks, Riley

 

[DotNetGnat]

go ahead and create a simple file...something like this...

<%
Response.write "Just Testing"
%>

and run both on your server and on client's server...and see if you still see the same behavior...if not then you have additional unmatched %> on your 20 pages(include or main files)...

-DNG

 

[riley3]

I’m embarrassed that I didn’t test like that before posting. I generally have Response.Write’s all over the place. I did what you suggested and it looks ok so I must have something wrong on each page. Seems odd to me that the same code looks ok on my server but not on the customer’s. I’ll continue to look and thanks for the help.

 

[DotNetGnat]

since its happening on all the pages...i aam thinking it has something to do with one of your include files...

-DNG

 

[riley3]

That's exactly what it is. My connection string is an include file and that's what I had to change yesterday when it was installed (from my server) to theirs. Darn - good thing I don't do this for a living. Thanks again for the help. Riley