ASP pages "not found"

I am in the process of moving several production sites to a new server. I
have successfully migrated all of the HTML content and all of the ASPX
content (.NET 3.5 / VS2008)

However, there are quite a few legacy ASP pages that we have not yet
converted. They continue to run properly on the original server. On the new
server, all we get is "not found" when attempting to browse them, even a
simple HTML file renamed with an ASP extension (to isolate avoid any
programming or ADO issues).

The ASP components appear to be properly registered in IIS 6.0 / Server 2003.

Do we need to run some type of procedure to enable ASP support?

The absence of any meaningful diagnostics is vexing.

Re: ASP pages "not found"

Have you allowed the ASP Web Service Extension?

What is logged in the IIS log file?

This may also be helpful:

"ASP files generates "404 - File or directory not found""
http://www.gafvert.info/notes/ASP404NotFound.htm

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


"theartiststillknownasgarvin" skrev i meddelandet
news:FE7FEF40-14B6-41ED-84A3-F7A07E73634F@microsoft.com...
>I am in the process of moving several production sites to a new server. I
> have successfully migrated all of the HTML content and all of the ASPX
> content (.NET 3.5 / VS2008)
>
> However, there are quite a few legacy ASP pages that we have not yet
> converted. They continue to run properly on the original server. On the
> new
> server, all we get is "not found" when attempting to browse them, even a
> simple HTML file renamed with an ASP extension (to isolate avoid any
> programming or ADO issues).
>
> The ASP components appear to be properly registered in IIS 6.0 / Server
> 2003.
>
> Do we need to run some type of procedure to enable ASP support?
>
> The absence of any meaningful diagnostics is vexing.

Re: ASP pages "not found"

Thank you, the extensions for ASP.NET v1.1, v 2.05, and FPSE 2002 were all
enabled.

ASP was not, and that was the problem, no solved.

Unsure how ASP.NET and FPSE were enabled, perhaps those are the defaults, or
not.

A lot has changed from my earlier days where everything was enabled
until/unless you locked them down



"Kristofer Gafvert" wrote:

> Have you allowed the ASP Web Service Extension?
>
> What is logged in the IIS log file?
>
> This may also be helpful:
>
> "ASP files generates "404 - File or directory not found""
> http://www.gafvert.info/notes/ASP404NotFound.htm
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> "theartiststillknownasgarvin" skrev i meddelandet
> news:FE7FEF40-14B6-41ED-84A3-F7A07E73634F@microsoft.com...
> >I am in the process of moving several production sites to a new server. I
> > have successfully migrated all of the HTML content and all of the ASPX
> > content (.NET 3.5 / VS2008)
> >
> > However, there are quite a few legacy ASP pages that we have not yet
> > converted. They continue to run properly on the original server. On the
> > new
> > server, all we get is "not found" when attempting to browse them, even a
> > simple HTML file renamed with an ASP extension (to isolate avoid any
> > programming or ADO issues).
> >
> > The ASP components appear to be properly registered in IIS 6.0 / Server
> > 2003.
> >
> > Do we need to run some type of procedure to enable ASP support?
> >
> > The absence of any meaningful diagnostics is vexing.
>
>

Re: ASP pages "not found"

http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Ba sics_of_IIS6_Tro=
ubleshooting.aspx

The most meaningful diagnostics for IIS remains its various log files
-- web, httperr, and event. See the blog entry for details and
rationale.

I suspect you want meaningful diagnostic error response returned for
your request that returns 404, but unfortunately, that would have been
a security vulnerability. This is the difference between a purely
client-side UI vs a client-server interaction like HTTP.

Your expectation that doing something in a client UI and having any
resulting error message being displayed actionable is quite correct.
However, when you translate that paradigm into a client/server
scenario, displaying such error messages on the client-side UI has two
major problems:
1. The error is meaningless to the vast majority of clients since they
have no access to the server configuration
2. The error is meaningful to some clients other than yourself, and
these clients intend to use this disclosure of information
vulnerability against your server/configuration

Given this reality,
- for server errors executing code, servers should really just send
"error occurred, contact the server administrator"
- for security errors, servers should send "404 not found". This is
exactly what IIS6 and later do.
- for other HTTP-level status codes, continue sending back innocuous
static error files

I realize that this is confusing relative to IIS versions prior to
IIS6 because those versions just displayed the detailed error back to
the client, so one can use the resulting HTML content in a web browser
to diagnose issues. However, from IIS6 onwards, log files are the way
to go.

As you've said, a lot has changed from the earlier days. This is just
another one of those changes in procedure that we thought through
before we made the change.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Jan 19, 10:16=A0am, theartiststillknownasgarvin
wrote:
> Thank you, the extensions for ASP.NET v1.1, v 2.05, and FPSE 2002 were all=

> enabled.
>
> ASP was not, and that was the problem, no solved.
>
> Unsure how ASP.NET and FPSE were enabled, perhaps those are the defaults, =
or
> not.
>
> A lot has changed from my earlier days where everything was enabled
> until/unless you locked them down
>
>
>
> "Kristofer Gafvert" wrote:
> > Have you allowed the ASP Web Service Extension?
>
> > What is logged in the IIS log file?
>
> > This may also be helpful:
>
> > "ASP files generates "404 - File or directory not found""
> >http://www.gafvert.info/notes/ASP404NotFound.htm
>
> > --
> > Regards,
> > Kristofer Gafvert
> >http://www.gafvert.info/iis/- IIS Related Info
>
> > "theartiststillknownasgarvin" skrev i meddelandet=

> >news:FE7FEF40-14B6-41ED-84A3-F7A07E73634F@microsoft.com...
> > >I am in the process of moving several production sites to a new server.=
I
> > > have successfully migrated all of the HTML content and all of the ASPX=

> > > content (.NET 3.5 / VS2008)
>
> > > However, there are quite a few legacy ASP pages that we have not yet
> > > converted. They continue to run properly on the original server. On th=
e
> > > new
> > > server, all we get is "not found" when attempting to browse them, even=
a
> > > simple HTML file renamed with an ASP extension (to isolate avoid any
> > > programming or ADO issues).
>
> > > The ASP components appear to be properly registered in IIS 6.0 / Serve=
r
> > > 2003.
>
> > > Do we need to run some type of procedure to enable ASP support?
>
> > > The absence of any meaningful diagnostics is vexing.- Hide quoted text=
-
>
> - Show quoted text -

Re: ASP pages "not found"

No, IIS defaults have everything disabled other than static content.

The reason ASP.Net is enabled is because when you installed ASP.Net,
it automatically enabled itself.
The reason FPSE is enabled probably because tools like Visual Studio
use it to remotely publish projects -- so if you ran their remote
server setup, it'd enable FPSE.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Jan 19, 10:16=A0am, theartiststillknownasgarvin
wrote:
> Thank you, the extensions for ASP.NET v1.1, v 2.05, and FPSE 2002 were all=

> enabled.
>
> ASP was not, and that was the problem, no solved.
>
> Unsure how ASP.NET and FPSE were enabled, perhaps those are the defaults, =
or
> not.
>
> A lot has changed from my earlier days where everything was enabled
> until/unless you locked them down
>
>
>
> "Kristofer Gafvert" wrote:
> > Have you allowed the ASP Web Service Extension?
>
> > What is logged in the IIS log file?
>
> > This may also be helpful:
>
> > "ASP files generates "404 - File or directory not found""
> >http://www.gafvert.info/notes/ASP404NotFound.htm
>
> > --
> > Regards,
> > Kristofer Gafvert
> >http://www.gafvert.info/iis/- IIS Related Info
>
> > "theartiststillknownasgarvin" skrev i meddelandet=

> >news:FE7FEF40-14B6-41ED-84A3-F7A07E73634F@microsoft.com...
> > >I am in the process of moving several production sites to a new server.=
I
> > > have successfully migrated all of the HTML content and all of the ASPX=

> > > content (.NET 3.5 / VS2008)
>
> > > However, there are quite a few legacy ASP pages that we have not yet
> > > converted. They continue to run properly on the original server. On th=
e
> > > new
> > > server, all we get is "not found" when attempting to browse them, even=
a
> > > simple HTML file renamed with an ASP extension (to isolate avoid any
> > > programming or ADO issues).
>
> > > The ASP components appear to be properly registered in IIS 6.0 / Serve=
r
> > > 2003.
>
> > > Do we need to run some type of procedure to enable ASP support?
>
> > > The absence of any meaningful diagnostics is vexing.- Hide quoted text=
-
>
> - Show quoted text -

Re: ASP pages "not found"

Hi Tommy,

After ASP web extension is enabled, do you still meet any error or problem
for the migration?

If so, please don't hesitate to post the details here. We will be glad to
be of assistance.

By the way, please make sure 'Show friendly HTTP error message' is disabled
in IE Internet Options->Advanced when you perform ASP related
troubleshooting.

Have a great week.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Re: ASP pages "not found"

All is okay.

There are two primary complications:

1) I am the software developer and my expertise lies elsewhere, but the
systems support company is not sufficiently knowledable in these areas, and
the client is too small to invest in full-time support.

2) My history that of MCSE, vintage 1994 and MCSD, vintage 1995, and as has
been pointed out, there is a total reversal in terms of "everything enabled
out of the box" to "everything locked down" until set otherwise. My past
expertise (certified in IIS 3.0) works against me, I need to forget every
"truth" that I used to know. With age, that process is proceeding well

""WenJun Zhang[msft]"" wrote:

> Hi Tommy,
>
> After ASP web extension is enabled, do you still meet any error or problem
> for the migration?
>
> If so, please don't hesitate to post the details here. We will be glad to
> be of assistance.
>
> By the way, please make sure 'Show friendly HTTP error message' is disabled
> in IE Internet Options->Advanced when you perform ASP related
> troubleshooting.
>
> Have a great week.
>
> Sincerely,
>
> WenJun Zhang
>
> Microsoft Online Community Support
>
> ==================================================
>
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at:
>
> http://msdn.microsoft.com/subscriptions/support/default.aspx .
>
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Re: ASP pages "not found"

Tommy,

That's good news. Glad to hear the issue has been resolved yet.

That's the truth the newer IIS versions have more and more consideration
and enhancement on security restriction/lockdown. IIS team believes this is
on the correct path because the lockdown policy not only bring benefits on
security but also on performance and stability(e.g: we can only include
required components on IIS7).

Anyway whenever you meet any IIS related issues in future, please don't
hesitate to post them in the newgroup again. We are pleased to be of
assistance and you are always welcome.

Have a great day!

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.