"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

"Jody" <J***@discussions.microsoft.com> wrote in message
news:563029DF-15EF-4EE8-8D3D-5FCA50B3F48D@microsoft.com...
> 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

"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" <J***@discussions.microsoft.com> wrote in message
> news:563029DF-15EF-4EE8-8D3D-5FCA50B3F48D@microsoft.com...
> > 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
>
>
>

> 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" <J***@discussions.microsoft.com> wrote in message
>> news:563029DF-15EF-4EE8-8D3D-5FCA50B3F48D@microsoft.com...
>> > 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
>>
>>
>>

"Ken Schaefer" wrote:

> "Jody" <J***@discussions.microsoft.com> wrote in message
> news:1C3E68C9-506D-48EF-ADA7-6773C153B10D@microsoft.com...
> > 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" <J***@discussions.microsoft.com> wrote in message
> >> news:563029DF-15EF-4EE8-8D3D-5FCA50B3F48D@microsoft.com...
> >> > 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
> >>
> >>
> >>
>
>
>

"Jody" <J***@discussions.microsoft.com> wrote in message
news:4C1BAAB9-406B-4EDD-91EB-3C406FFED515@microsoft.com...
> 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" <J***@discussions.microsoft.com> wrote in message
>> news:1C3E68C9-506D-48EF-ADA7-6773C153B10D@microsoft.com...
>> > 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" <J***@discussions.microsoft.com> wrote in message
>> >> news:563029DF-15EF-4EE8-8D3D-5FCA50B3F48D@microsoft.com...
>> >> > 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
>> >>
>> >>
>> >>
>>
>>
>>

"Daniel Crichton" wrote:

> Jody wrote  on Wed, 12 Jul 2006 20:31:01 -0700:
>
> > 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.
>
> Listen to Ken, he knows what he's talking about. I've got a 500-100.asp page
> on my site that shows internal users the complete error message and
> additional debugging info, and the general public a simple "an error has
> occurred" message. I can't remember where I got the original code I
> modified, but the MS Support site is a good place to start.
>
> Dan
>
>
>

"Jody" <J***@discussions.microsoft.com> wrote in message
news:C485C39A-C364-4070-B925-E66E72FC6BA8@microsoft.com...
> Thanks to you both.  As far as reading ALL the IIS documentation much of
> it
> is not related to what I am needing to know and would take days to sort
> through. I am failry familure with IIS arelady it is only this part that I
> was not sure about.  I still do not have an answer to my question if the
> ASP
> 0311 error is in fact a 500-100 error or not??  I do appreciate Ken's
> Explanation however it was not my intention to ask for a full on tutorial.
>
> I did find the radio button in
> IIS/Properties/HomeDirectory/Configuration/Debugging tab that allows you
> to
> select what kind of messages are sent to the client or not.  Perhaps this
> is
> all I needed?  I am waiting on the webmaster to test this by forcing an
> error
> and see what happens.
>
> "Daniel Crichton" wrote:
>
>> Jody wrote  on Wed, 12 Jul 2006 20:31:01 -0700:
>>
>> > 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.
>>
>> Listen to Ken, he knows what he's talking about. I've got a 500-100.asp
>> page
>> on my site that shows internal users the complete error message and
>> additional debugging info, and the general public a simple "an error has
>> occurred" message. I can't remember where I got the original code I
>> modified, but the MS Support site is a good place to start.
>>
>> Dan
>>
>>
>>

"Ken Schaefer" wrote:

> > As far as reading ALL the IIS documentation much of it
> > is not related to what I am needing to know and would take days to sort
> > through.
>
> Rubbish. It would probably take you about 5-10 minutes to read the relevant
> parts.
>
> > I still do not have an answer to my question if the ASP
> > 0311 error is in fact a 500-100 error or not??
>
> You could have simply *tested* this yourself.
>
> Create your own custom 500-100 error page (it doesn't need to do anything
> special - it could just say "this is a test page"). Then create an ASP page
> that times out (it could just loop for 90 seconds doing nothing). Then see
> if your custom error page is loaded or not.
>
> That would have taken 10 seconds to create the page. 10 seconds to put it on
> a test server. 90 seconds of waiting. All up, about 2 minutes of your life
> to test.
>
> We are not here to answer every question about everything. That's what
> manuals are for. I am not going to retype stuff out of manuals and the
> Microsoft KB - at some point you need to put in some effort yourself, to
> solve what is ultimately your problem and not ours.
>
> Cheers
> Ken
>
>
> "Jody" <J***@discussions.microsoft.com> wrote in message
> news:C485C39A-C364-4070-B925-E66E72FC6BA8@microsoft.com...
> > Thanks to you both.  As far as reading ALL the IIS documentation much of
> > it
> > is not related to what I am needing to know and would take days to sort
> > through. I am failry familure with IIS arelady it is only this part that I
> > was not sure about.  I still do not have an answer to my question if the
> > ASP
> > 0311 error is in fact a 500-100 error or not??  I do appreciate Ken's
> > Explanation however it was not my intention to ask for a full on tutorial.
> >
> > I did find the radio button in
> > IIS/Properties/HomeDirectory/Configuration/Debugging tab that allows you
> > to
> > select what kind of messages are sent to the client or not.  Perhaps this
> > is
> > all I needed?  I am waiting on the webmaster to test this by forcing an
> > error
> > and see what happens.
> >
> > "Daniel Crichton" wrote:
> >
> >> Jody wrote  on Wed, 12 Jul 2006 20:31:01 -0700:
> >>
> >> > 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.
> >>
> >> Listen to Ken, he knows what he's talking about. I've got a 500-100.asp
> >> page
> >> on my site that shows internal users the complete error message and
> >> additional debugging info, and the general public a simple "an error has
> >> occurred" message. I can't remember where I got the original code I
> >> modified, but the MS Support site is a good place to start.
> >>
> >> Dan
> >>
> >>
> >>
>
>
>