how do i fix this error in asp 2.0

[Guest]

Failed to execute request because the App-Domain could not be created. Error:
0x80070005 Access is denied.


Failed to initialize the AppDomain:/LM/W3SVC/5/Root

Exception: System.IO.FileLoadException
Message: Could not load file or assembly 'System.Web, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
Access is denied.
StackTrace: at System.AppDomain.CreateInstance(String assemblyName,
String typeName)
at
System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String
appId, IApplicationHost appHost, HostingEnvironmentParameters
hostingParameters)
at
System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String
appId, IApplicationHost appHost, HostingEnvironmentParameters
hostingParameters)

thanks

 

[Teemu Keiski]

Hi,

check that ASPNET user has read/write permissions to folder (and subfolders)
on %SYSTEM%/Microsoft.NET. In this case of course the interesting one is
v2.xxx folder

 

[R. Brian Lindahl]

i've got the same problem. Windows 2003 x64, dotnet 64 (netfx64.exe v.
2.0.50215.45 from public download). i checked the %SYSTEM%\Microsoft.Net
folders, and added the aspnet user with full control to the entire tree.
didn't help.

any further suggestions? TIA

 

[Juan T. Llibre]

Check your current permissions against this article which spells
out the permissions needed for all essential ASP.NET directories:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod15.asp

See Table 1: Required NTFS permissions.

 

[R. Brian Lindahl]

Didn't help.

anything else I can try? i'm about at the point of starting over with a
fresh install (not that this one is that old - only installed win2003 a week
ago).

 

[Juan T. Llibre]

re:

Didn't help.

*All* the recommended permissions for the account which
your ASP.NET install is using are set correctly ?

Did you follow the special instructions for the GAC ?
Did you use the correct ASP.NET version number ?

( The examples use ASP.NET 1.0 version's directory,
but your *current* version's directory must be used. )

 

[R. Brian Lindahl]

i don't have any special settings for the asp.net account - i checked
settings for the auto-generated ASPNET account.

*All* the recommended permissions for the account which
your ASP.NET install is using are set correctly ?
yes

Did you follow the special instructions for the GAC ?

yes. i turned off shfusion.dll and set the properties via explorer.

Did you use the correct ASP.NET version number ?
( The examples use ASP.NET 1.0 version's directory,
but your *current* version's directory must be used. )

i made sure all 3 versions have the right settings (1.1, 2.0 (64), and 2.0
(32))

this was a fresh 2003 enterprise x64 install a week ago. i've installed sql
server 2000 (x86) and turned on the app server, file server, and streaming
media server roles, as well as installing the FTP service. the only 3rd
party stuff installed is winrar and argosoft mail server.

this same machine was working fine a couple of weeks ago. i had to remove a
secondary hard disk, which messed up the PDC role i had installed in that
instance, so i reinstalled from scratch. the only difference i can think of
is that before, I had installed .net 2.0 as part of installing sql server
2005 june ctp instead of doing it by itself this time. we decided not to use
sql 2005 at this time.

 

[Guest]

Has same issue... adding the Network Service account with read/write rights
to the website root folder fixed it for me

 

[Hans Kesting]

Has same issue... adding the Network Service account with read/write

rights to the website root folder fixed it for me

*write* access to the complete site seems a bit much. Just a *read* should
be
enough (and is needed).
Only if you really are writing files (logfiles, uploaded documents, ..),
*then* you
can (and must) add write-rights, but only to the directories you will write
to.

Hans Kesting

 

[Guest]

Ok, removed the write access and it still works

*write* access to the complete site seems a bit much. Just a *read* should
be
enough (and is needed).
Only if you really are writing files (logfiles, uploaded documents, ..),
*then* you
can (and must) add write-rights, but only to the directories you will write
to.

Hans Kesting

 

[jebuskrust]

I registered to this website to point out the same problem that we experienced.. And here was our solution .. Solution for us was to ensure that the application pool user is set to never expire.. What ended up happening was that, the password for the application pool user expired and had to be reset.

Seriously people , please dont fill the internet with crap, these posts werent real resolutions.. They were temporary fixes.. I dont like googling for 3 months just to find a real resolution.. I had to figure this one out on my own.