IIS custom errors stop working after adding web.config

We have an IIS 6.0 server running mostly classic ASP applications and use
custom errors configured in IIS manager. However, recently we added a few
ASP.NET applications to the server and use a web.config file at the root of
the site for all of the .NET inherit their connections strings. After adding
these .NET applications, the custom error pages for classic ASP apps no
longer work. I know that you can configure a web.config with tags for custom
errors but does that, by default, override the custom errors configured in
IIS. Can you have IIS custom errors and web.config custom error coexisting
on the same machine? Thanks for any advice you can offer.

RE: IIS custom errors stop working after adding web.config

This issue has been resolved. The error we were getting was "The specified
request cannot be executed from current Application Pool" and there is a
registry key that can be added to correct it. See these links.

http://www.microsoft.com/technet/community/columns/insider/i isi0905.mspx#EJD

http://blogs.msdn.com/rakkimk/archive/2006/09/01/735684.aspx




"Ryan" wrote:

> We have an IIS 6.0 server running mostly classic ASP applications and use
> custom errors configured in IIS manager. However, recently we added a few
> ASP.NET applications to the server and use a web.config file at the root of
> the site for all of the .NET inherit their connections strings. After adding
> these .NET applications, the custom error pages for classic ASP apps no
> longer work. I know that you can configure a web.config with tags for custom
> errors but does that, by default, override the custom errors configured in
> IIS. Can you have IIS custom errors and web.config custom error coexisting
> on the same machine? Thanks for any advice you can offer.

Re: IIS custom errors stop working after adding web.config

Did someone map the classic ASP script mapping to asp.net ISAPI?

--

Best regards,

Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield


"Ryan" wrote in message
news:F120A7E2-E1F2-4968-A04F-34B92C0ED681@microsoft.com...
> We have an IIS 6.0 server running mostly classic ASP applications and use
> custom errors configured in IIS manager. However, recently we added a few
> ASP.NET applications to the server and use a web.config file at the root
> of
> the site for all of the .NET inherit their connections strings. After
> adding
> these .NET applications, the custom error pages for classic ASP apps no
> longer work. I know that you can configure a web.config with tags for
> custom
> errors but does that, by default, override the custom errors configured in
> IIS. Can you have IIS custom errors and web.config custom error
> coexisting
> on the same machine? Thanks for any advice you can offer.

Re: IIS custom errors stop working after adding web.config

Thanks for your comment. I don't think that was done in our environment.
Actually, I couldn't even tell you how to do that. What would be the effect?

"Steve Schofield" wrote:

> Did someone map the classic ASP script mapping to asp.net ISAPI?
>
> --
>
> Best regards,
>
> Steve Schofield
> Windows Server MVP - IIS
> http://weblogs.asp.net/steveschofield
>
>
> "Ryan" wrote in message
> news:F120A7E2-E1F2-4968-A04F-34B92C0ED681@microsoft.com...
> > We have an IIS 6.0 server running mostly classic ASP applications and use
> > custom errors configured in IIS manager. However, recently we added a few
> > ASP.NET applications to the server and use a web.config file at the root
> > of
> > the site for all of the .NET inherit their connections strings. After
> > adding
> > these .NET applications, the custom error pages for classic ASP apps no
> > longer work. I know that you can configure a web.config with tags for
> > custom
> > errors but does that, by default, override the custom errors configured in
> > IIS. Can you have IIS custom errors and web.config custom error
> > coexisting
> > on the same machine? Thanks for any advice you can offer.
>
>