Re: IIS 6 and Server 2003 ASP.NET apps don't run well...sort of
- From: "Kevin Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 May 2005 11:00:09 -0400
Hi Hank,
So, you're using IIS Admin to create a new virtual directory that is
somewhere else on the computer than under Inetpub? And then you're using IIS
Admin to create an application from that virtual directory? And this new
virtual directory is not configured as a web site, but a virtual directory
under another web site, or is it a new web site? I just want to be sure
we're talking apples and apples here.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
"HankD" <MrHankD@xxxxxxxxx> wrote in message
news:1115641879.775936.157220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the replies, I understand what you are saying (killing a fly
with a sledgehammer etc.) That is why I am thinking something is a
foot. Basically I am building the application on my local moving it to
the test environment (which is a 2000 server and IIS 5 and works fine)
finally moving to production. I make the move to production the same as
when I move from local to test. Moving the aspx files and bin to the
production server and then using IIS to make the application. One
thing I am also doing is that my root dir is not under wwwroot. I have
set it up in a different directory. Do you think that may be the
problem?
Thanks for the help.
Kevin Spencer wrote:
> I have to correct myself. It isn't your app that is causing the
problem; I
> misread. Installing a new app does this? How are you installing a new
app?
>
> There are several ways of creating a new ASP.Net application. One is
using
> Visual Studio.Net. One is to create a folder under wwwroot on your
hard
> drive, and use IIS Admin to create the application. There are several
other
> methods as well, including using IIS Admin to do the entire thing.
>
> Hope you got a laugh out of my analogy.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> What You Seek Is What You Get.
>
> "HankD" <MrHankD@xxxxxxxxx> wrote in message
> news:1115397823.927012.176340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I get the following error when I add a new application to our server.
> If I run aspnet_regiis -i it takes care of the problem but when I add
> another application I get the same error for the second application.
> The first app works fine. If I run aspnet_regiis -i the second app
> works fine. I thought I needed to run aspnet_regiis -i only once not
> with every new application. Does anyone else have this problem?
Things
> just don't seem right, I know in on my IIS 5 Windows 2000 Server it
was
> a one time deal.
>
> Thanks
>
>
> The error I get is below:
> Access to the path
> "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
> Files\blogapp\5fc9e323\1ff3aeee" is denied.
> Description: An unhandled exception occurred during the execution of
> the current web request. Please review the stack trace for more
> information about the error and where it originated in the code.
>
>
> Exception Details: System.UnauthorizedAccessException: Access to
the
> path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
ASP.NET
> Files\blogapp\5fc9e323\1ff3aeee" is denied.
>
>
> ASP.NET is not authorized to access the requested resource. Consider
> granting access rights to the resource to the ASP.NET request
identity.
> ASP.NET has a base process identity (typically {MACHINE}\ASPNET on
IIS
> 5 or Network Service on IIS 6) that is used if the application is not
> impersonating. If the application is impersonating via <identity
> impersonate="true"/>, the identity will be the anonymous user
> (typically IUSR_MACHINENAME) or the authenticated request user.
.
- Follow-Ups:
- References:
- Prev by Date: Julian Calendar
- Next by Date: Re: document.getElementsByName problem
- Previous by thread: Re: IIS 6 and Server 2003 ASP.NET apps don't run well...sort of
- Next by thread: Re: IIS 6 and Server 2003 ASP.NET apps don't run well...sort of
- Index(es):
Relevant Pages
|
