"The resource cannot be found" error accessing a .aspx file

I am having a really strange problem. I have a site setup in a virtual
directory that fails with the error below. It works on other web servers
that are network load balanced with this server. I can go right to the
default.aspx right in the ISS Manager and right-click browse and the error
still comes up. I re-copied the folder over from a working server and
checked IIS and NTFS permissions and it all matches. I recreated the
virtual directory as well. I can pull up a .htm file from the virtual
directory and I can pull up other .aspx files from other sites on the
server. But no aspx file work at all in this virtual directory. I
re-installed ASP.NET on the server as well. I looked in the event log and
logfiles and found nothing.

Any ideas?


Server Error in '/app' Application.
----------------------------------------------------------------------------
----

The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make sure that
it is spelled correctly.

Requested Url: /app/Default.aspx


----------------------------------------------------------------------------
----
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032

I figured it out.

Under the root path in IIS configuration, under "Home Directory"
under the field "local path". "c:\inetpub\mywebsite\" is not the same
as "c:\inetpub\mywebsite" apparently now. My site came back alive as
soon as I removed the trailing backslash so that the path now says
"c:\inetpub\mywebsite".

Who would know?


"Steve M" <steve@donotreply.com> wrote in message
news:%23v9RO%23PFFHA.3984@TK2MSFTNGP14.phx.gbl...[color=blue]
> I am having a really strange problem. I have a site setup in a virtual
> directory that fails with the error below. It works on other web servers
> that are network load balanced with this server. I can go right to the
> default.aspx right in the ISS Manager and right-click browse and the error
> still comes up. I re-copied the folder over from a working server and
> checked IIS and NTFS permissions and it all matches. I recreated the
> virtual directory as well. I can pull up a .htm file from the virtual
> directory and I can pull up other .aspx files from other sites on the
> server. But no aspx file work at all in this virtual directory. I
> re-installed ASP.NET on the server as well. I looked in the event log and
> logfiles and found nothing.
>
> Any ideas?
>
>
> Server Error in '/app' Application.
> --------------------------------------------------------------------------[/color]
--[color=blue]
> ----
>
> The resource cannot be found.
> Description: HTTP 404. The resource you are looking for (or one of its
> dependencies) could have been removed, had its name changed, or is
> temporarily unavailable. Please review the following URL and make sure[/color]
that[color=blue]
> it is spelled correctly.
>
> Requested Url: /app/Default.aspx
>
>
> --------------------------------------------------------------------------[/color]
--[color=blue]
> ----
> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;[/color]
ASP.NET[color=blue]
> Version:1.1.4322.2032
>
>[/color]

"Steve M" <steve@donotreply.com> wrote in message
news:<ODPjALQFFHA.1084@tk2msftngp13.phx.gbl>...
[color=blue]
> I figured it out.
>
> Under the root path in IIS configuration, under "Home Directory"
> under the field "local path". "c:\inetpub\mywebsite\" is not the same
> as "c:\inetpub\mywebsite" apparently now. My site came back alive as
> soon as I removed the trailing backslash so that the path now says
> "c:\inetpub\mywebsite".
>
> Who would know?
>[/color]

Did you by any means install the latest security patches from
Microsoft like the Security Update for Microsoft .NET Framework,
Version 1.1 Service Pack 1 (KB886903)? After I installed this (and
other patches) and rebooted the server, all sites worked except the
one utilizing .Net. Luckily I discovered this post and it solved my
problem too. Works like a charm again.

Grtz,

Mac