G
Grant Harmeyer
I have a Win2K server set up with .NET 1.1, IIS5, and I run a few
development test sites on this server for deployment elsewhere. Up until
now, there was no issue with the sites residing in the Inetpub directory on
the sys partition. However, we are starting to consume valuable disk space
on the sys partition. So, I have moved one of the sites (a low priority one)
to a network drive (and different partition) that is still on the same
physical server, just not the sys partition.
The .NET runtime now has what I beleive to be a security problem with the
site when it is being hosted from this location. It states that it can't
load the type (ASPX CodeBehind) of the page because of a SecurityException
that can be fixed by adding a node to my Web.Config file. But I am unable to
find any documentation as to what this node is, or where it is to be placed
in the Web.Config file. If I were to guess, I would say this may be an
instance where the web application needs to impersonate an account with the
correct tokens for the app to run, but I'm a bit lost right now. Any quick
fixes for hosting sites off of a network drive?
P.S. I have ensured my ACL file settings on the site are correct, as well as
IIS perms ( twice ;-) )
Grant Harmeyer
development test sites on this server for deployment elsewhere. Up until
now, there was no issue with the sites residing in the Inetpub directory on
the sys partition. However, we are starting to consume valuable disk space
on the sys partition. So, I have moved one of the sites (a low priority one)
to a network drive (and different partition) that is still on the same
physical server, just not the sys partition.
The .NET runtime now has what I beleive to be a security problem with the
site when it is being hosted from this location. It states that it can't
load the type (ASPX CodeBehind) of the page because of a SecurityException
that can be fixed by adding a node to my Web.Config file. But I am unable to
find any documentation as to what this node is, or where it is to be placed
in the Web.Config file. If I were to guess, I would say this may be an
instance where the web application needs to impersonate an account with the
correct tokens for the app to run, but I'm a bit lost right now. Any quick
fixes for hosting sites off of a network drive?
P.S. I have ensured my ACL file settings on the site are correct, as well as
IIS perms ( twice ;-) )
Grant Harmeyer