ASP errors are displaying in the HTML of my page

I really hope someone can help me with this, because I am about to crazy trying to figure this out.

I have a webpage that has an error in it (on purpose mind you) because I am trying to create a custom IIS 500.100 error page. For some reason, on one of our servers, the error message displays in the HTML for the webpage. See this image:
Error In HTML

Notice how the first part of the HTML is displayed, then the error message and then nothing after that.

On on a different web server I get the IIS 500.100 default page:
Default IIS 500.100 Error

What server setting do I have to change to make the first server dispaly the 500.100 Error page? I have been comparing IIS settings all night and everything is the same.

Has anyone run accross this?

Edit: fixed links

hi
can u tell me in details what is your problem

In detail?

I have an error on my page (on purpose).

On ONE server it displays the error in the HTML of the page (say index.asp). It never redirects to the standard IIS 500.100 error page.

The same pge on another server displays the IIS 500.100 error page when it encounters the error.

I want the first server to behave like the second. Does anyone know of the setting that affects how and where the error messages are displayed. See links to screenshots in first post.

You should check the custom error configuration on the servers.

Could you be a little more specific? If you are talking about Custom Error Pages (or the place you define error pages) I have. They are all set to their default pages. And they all match the other server that is working the way I want it too.

Compare all the IIS configurations between the servers then. Look in the web application configuration, there are more asp error settings there.

I don't know what you mean by displaying in the html of the page.

I have compared both server settings. If you look at my screen shots:

The first server dispalys the page up until the error and then displays the error message. It never forwards to an error page.

The second server forwards to the standard IIS 500-100 error page upon encountering the error.

If you'll notice the errors you show are two completely unrelated errors, I don't know if that matters.

In one case the asp page is able to load and execute up to the error, in the other case the asp page is unable to load. I don't know what may make the two computers react differently if IIS is configured the same on both, sorry. Maybe there is some other difference like database drivers, etc.

HI,

regarding Ur First bug shown here:

The Problem is with ur dbconnect.asp, which u have included,(may be for connection, check ur username and password with connection string , which shows the error is in line 13)

regarding ur second pbm:

Check out ur server port, right click "My computer" icon in ur desktop, choose the option "Manage", then select IIS , and check the port of ur localhost. U have given as "localhost:9000". Check whether that is correct. Then, check ur included file , dbconnect.asp, ( hope ur connection string may not be the right one, since u r getting an error as "the table or view doesnt exist", so either the table doesnt exist, or the connection string is not correct)

Note:
Hope the problem is not with IIS, and may be with the connection string.

Thanks for everyone who has tried to help. Since I am intern, I do not have rigts to just re-install a fresh copy of IIS on our test server. But, I got my co-workers to do it anyway. Now it is working as it should (forwarding to the error page). I was just hoping someone knew of a setting that told IIS not to forward to the error page, but just display the error on the current page.

To the post above: The errors were created on purpose. I wanted to show that on one computer the errors are forwarded to the IIS 500.100 error page and on the other server the error is displayed right on the page that was trying to load (never forwards). Thanks though =)