"Request could not be executed because application domain could not be created" is a common.NET error in IIS.
The server application is unavailable
The Web application you are trying to access on this Web server is currently unavailable. Please click the "Refresh" button in your Web browser to retry your request.
Administrator note: An error message detailing why this particular request failed can be found in the system event log of the Web server. Check this log entry to find out what caused the error.
The solutions provided online are summarized as follows:
1:
When.NET 2.0 and 1.1 are shared, "appears". Server Application unavailable" The mistake.
It's actually a process pool call conflict problem, if you access two applications, respectively 2.0 and 1.1, and they share a process pool,
IIS cannot parse both versions at the same time, and the error above occurs.
The solution:
Change the process pool of one of them, such as changing the process pool of the 2.0 application to ASP.NET 2.0. That's it.
2:
Re-register with.NET, aspnet_regiis.exe in NETFrameworkv2.0.50727 Run it and re-register.net aspnet_regiis.exe -u uninstall aspnet_regiis Sometimes it's just a matter of restarting the server.
3:
After 2.0 is installed, there is an additional ASP.NET TAB in the property Settings of the virtual directory of IIS, where the runtime is adjusted to 2.0, and the 1.1 runtime is used by default.
4:
This is a permission issue,
First check the properties of the application pool to see what user it is running as, typically a NETWORK SERVICE, and then make sure that the user pairs. NET Framework 2.0 directories have access, as they should. Directory is systemroot:WindowsMicrosoft.NET Frameworks 2.0. XXXX
In fact, the permission problem is the most common. Most of the problem is not with your IIS Settings, but with your disk permissions. Try giving NETWORK SERVICE user access to your.NET web directory. If not, give Everyone with the highest authority full control and see if it is normal. Not if we give it maximum access. That must not be a disk permission issue. Note that some.NET web applications require access to the parent directory!
For security reasons, we always want websites to assign minimal permissions. It can run the program stably and reliably, and achieve maximum safety. Finally, semi-professional server administrators are advised to take advantage of system tools, such as regularly analyzing logs with event viewers. It's often the best way to find out why. Never restart a server when you can't fix a problem. Don't put your hopes on it. Look online, learn, and analyze the possibilities for yourself. Then try it little by little without compromising the security of the system, so that you can improve your skills.
Technorati Tags: Server, System, Security, Permissions,IIS,.net