After hosting an ASP.NET 2.0 web application on a windows 2000 server(IIS 5). I was unable to browse the web site.
The following error message was displayed on the b
I discovered that when the web site folder was copied to the server it inherited the security permissions of the parent folder which only had permission for the Administrator, Administrators & System accounts.
I added
With Read & Execute, List Folder Contents and Read permissions.
Even though the problem is resolved I still have some questions
It's clear from the third event log entry that the ApplicationManager fails to create the HostingEnvironment which is in the System.Web assembly.
Since FileLoadException is thrown for System.Web it seems like the ASP.NET worker process doesn't have access to the GAC folder.
Why is the FileLoadException thrown for accessing System.Web?
I had the same problem and it didn't go away with aspnet_regiis with -u and -i and many others suggested here. But after I cleaned “%windir%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files” folder and gave this folder read-write permissions to user from identity impersonate section in web.config, problem disappeared. It was not sufficient to give local ASPNET user those rights.
This error means that your code has thrown an exception that has either crashed IIS, or forced it to shut down. Common exceptions that cause this are OutOfMemoryException and StackOverflowException.
You're getting a FileLoadException, but there could be an underlying OutOfMemoryException or similar that's actually the root cause of that. Without knowing what you're trying to load, and the code that's inside it, it's impossible to tell what's actually causing your problem.
The first thing I would do to rule out a problem with the loading assembly, though, is to try and reflect over it in a test harness and see if the same problem happens. If so, then the problem is with the DLL that you're trying to load, not IIS.
From the looks of it you have an incorrect permission set for your ASP.NET installation. Typically the best bet it to just uninstall and re-install the ASP.NET portion. You can do this easily by the following.
That will uninstall ASP.NET and re-install, that should then establish the proper permissions for the account.