Temoprary ASP.NET Files access denied

[Guest]

Server Windows 2003. Created one web site, everything works fine. Copied the
content to another folder and created another web site pointing to the copied
contecnt for test purposes. Configuration is identical except that the test
site has a different IP and some path changes were made in web.config to
match the different location. First site still working fine, but test site
gets access denied trying to create folders under the Temporary ASP.NET Files
folder. Network Service and System have Full Control, ran iisreg -i,
restarted IIS. Still same problem. Maybe a probnlem with duplicate web app
names or duplicate dll names? Tried changeing the name of one of the app
folders and app name, but still got the same error. TIA

 

[Guest]

If you are not using impersonation then you need to give access to the ASPNET
account otherwise to the userID that is being impersonated.

 

[Guest]

The ASPNET account also has full control. Both the original and copied(test)
sites are configured the same as far as I can tell, what would account for
one working and one failing?

 

[Guest]

I think I stumbled acrosss the answer. I found a script that will display the
user that is actually trying to create the temp folders. I was surprised to
find that it was the "Connect As" account. I did not mention before that the
content is on a different server. When I checked the "Connect As" on the site
taht was not working, it was different and did not have NTFS permission to
create the temp files. I now have a new error, but I will wrestle with that a
while before I cry for help.

Thanks.

 

[Juan T. Llibre]

That the ASPNET account is not the one ASP.NET uses
when running under Windows Server 2003 ?

ASP.NET runs as the NT AUTHORITY\NETWORK SERVICE
account when running under W2K3.

 

[Juan T. Llibre]

You probably found my script.

Yes, verifying the identity ASP.NET is running as
is the first thing that ASP.NET programmers should do.

Knowing that saves a lot of headaches.

 

[Guest]

Apparently that changes in a configuration like ours. The content is not
local, but on another file server. The account used to connect to the remote
file share was also the account used to create the local temporary files.
Thanks for the identity script! That was the key.

lightcap

 

[Juan T. Llibre]

re:

The content is not local, but on another file server.

Yes, when a site's content is on a file server, and not on the web server itself,
the account ASP.NET runs as is the connecting machine's account.

re:

Thanks for the identity script! That was the key.

You're very much welcome!

 

[Guest]

Thanks Juan for this correction. I guess I have accidentally helped by
suggesting the ASPNET account even though it was not the right answer, though
it turned out to be the solution