Aug
18

Failed to execute request because the App-Domain could not be created

Author andy18    Category Windows-related     Tags

If you have a IIS server and ASP.Net is installed on the box but you are unable to load the site, and you have seen 1088 and 1344 event ID in your server event log as follow, check the Application Pool identity which runs the site and make sure the identity have read/execute permission on the NTFS folder permission which the web.config file are located.

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1088
Date: 8/18/2008
Time: 10:26:26 AM
User: N/A
Computer: ServerName1
Description:
Failed to execute request because the App-Domain could not be created. Error: 0×80070005 Access is denied.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1334
Date: 8/18/2008
Time: 10:26:43 AM
User: N/A
Computer: ServerName1
Description:
Failed to initialize the AppDomain:/LM/W3SVC/13434/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.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Activator.CreateInstance(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(String assemblyName, String typeName)
at System.AppDomain.CreateInstance(String assemblyName, String typeName)
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)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

3 Comments to “Failed to execute request because the App-Domain could not be created”

  • pandincus November 23, 2008 at 11:00 am

    This was exactly the information I needed to fix a major bug. Thank you!

  • andy18 November 24, 2008 at 4:30 pm

    Glad it works for you :-)

  • e_stylzz March 12, 2009 at 12:59 am

    This article was a life saver. Thanks so much!!!

Post comment