Re: Supressing Public ASP Error Codes

Hi Jody,

Please read the IIS documentation on custom error pages, and then come back
to us.

The purpose of a custom error page is that this custom page will be served
to the client when an error occurs *rather* that the customer seeing the
default.

For example, when a client requests a non-existant page, you can deliver a
custom 404 error page instead (404 is the HTTP status condition for File Not
Found).

500 errors conditions are "Internal Server Error". A 500-100 error is a
specific internal server error caused by an ASP related error.

So, you would create a custom 500-100 error page. When an ASP error occurs,
IIS will send this error page to the client, rather than the existing page +
error message that you are seeing at the moment

I'm not going to write out a whole tutorial on how to use IIS, because I
don't have time. That's what the online help is for. Please, read that, and
then get back to us on specific questions you might have.

Cheers
Ken


"Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4C1BAAB9-406B-4EDD-91EB-3C406FFED515@xxxxxxxxxxxxxxxx
The error I mentioned in my example below was not occuring on a seperate
"error Page'. The error text was added to the existing webiste page at
the
bottom as the page with the script error did finally display.

Also would an "ASP 0113" error be considered a 500-100 error? Just
wondering ig the leading zero makes this diffrent or not.

Thanks Ken

"Ken Schaefer" wrote:

"Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C3E68C9-506D-48EF-ADA7-6773C153B10D@xxxxxxxxxxxxxxxx
Thanks Ken,

If I understand you correctly, it is the 500-100.asp page that
determins
what error(s) are added to website pages should there be an error?

When an ASP-related error occurs, IIS will transfer control to whatever
is
configured as the error page for 500-100 type errors.


I do not understand what you mean by:

"Customise your website in IIS, so that the 500-100 error page points
to
your
page, and not the default one supplied with IIS."

What page do I point the 500-100.asp file to? The website has numerous
pages?

Create your own page that you would like displayed to users when an ASP
error occurs. Then configure IIS to use that page by changing the custom
errors property for 500-100 errors (500-100 errors are Internel Server
Errors generated by ASP-related problem).

Cheers
Ken



Thanks - Jody

"Ken Schaefer" wrote:

Create your own custom 500-100.asp error page.

Customise your website in IIS, so that the 500-100 error page points
to
your
page, and not the default one supplied with IIS.

Then your message will be displayed. Additionally, if you make the
custom
page an ASP page itself, you can use the ASPError object to get
details
about the error and have them emailed to you (or logged to a database,
event
log etc).

Take a look in c:\windows\help\iishelp\common\500-100.asp file for
some
ideas on how the ASPError object works.

Cheers
Ken

"Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:563029DF-15EF-4EE8-8D3D-5FCA50B3F48D@xxxxxxxxxxxxxxxx
P.S. This site is hosted on a dedicated Windows 2003 Server running
IIS
6.0.

"Jody" wrote:

I am the server Admin for a webmaster who designed a site in
Straight
ASP
using SQL Server 2000 SP4. I am not a literate ASP programmer and
the
webmaster is not very experienced in this area either.

So, I am soliciting some assistance with how to having
non-informative
ASP
error messages appearing to the public?

For example we recently encountered a permissions issues that
generated
the
following error message that was displayed at the bottom of the
website
web
page. Although this issue is resolved we want to prevent this kind
of
descriptive error code from being public.
For example:

Active Server Pages error 'ASP 0113'
Script timed out
/lectures.asp

All I have been able to find so far is the custom error pages in
IIS.
There
are a bunch of htm pages with various messages but none of them
have
any
error like the one above. The messages I am referring to are added
to
the
website page, they are not a separate error page as the ones in IIS
appear to
be. This leads me to believe that I am not looking in the correct
place.

I would greatly appreciate anyone pointing me in the right
direction.

Thanks - Jody








.

Relevant Pages

  • Re: Supressing Public ASP Error Codes
    ... IIS will transfer control to whatever is ... The website has numerous ... Create your own page that you would like displayed to users when an ASP ... Then configure IIS to use that page by changing the custom ...
    (microsoft.public.inetserver.iis.security)
  • Re: global.aspx Application_error does not fire on anything other than
    ... Another option is to simply set a custom page for 404 errors in IIS. ... Remember, .aspx files go through the ASP.NET ISAPI application; html, asp, etc. files don't. ...
    (microsoft.public.dotnet.framework.aspnet)
  • 404 Redirect Question
    ... I am building a directoy website which has over ... So what I want it to do is the 404 page ASP code will look at the page ... So in IIS I tried setting the Custom Errors 404 Message Type as File ...
    (microsoft.public.inetserver.asp.general)
  • 404 Redirect Question
    ... I am building a directoy website which has over ... So what I want it to do is the 404 page ASP code will look at the page ... So in IIS I tried setting the Custom Errors 404 Message Type as File ...
    (microsoft.public.inetserver.iis)
  • Re: Thnslicer does not work on Windows 2003
    ... I have adjusted the error to be custom and here is the exact message I get: ... Open IIS Help, which is accessible in IIS Manager, and search for topics titled Web Site Administration, and About Custom Error Messages. ... In the IIS Software Development Kit or at the MSDN Online Library, search for topics titled Debugging ASP Scripts, Debugging Components, and Debugging ISAPI Extensions and Filters. ...
    (microsoft.public.sqlserver.olap)