Previous Next

• 12-12-2006, 5:15 AM

  Positron Joined on 04-11-2006, 11:29 AM Posts 1

  Server Application Unavailable - Failed to execute request because the App-Domain could not be created. Error: 0x8007000e Not enough storage is available to complete this operation. Reply Contact Hello everyone, Here is the scenario: Our production server (Windows Server 2003 Enterprise SP1 64 bit) has been running a Classic ASP application for years. We started recently to add new portions of the application in ASP.NET 2.0. It took some time to figure out how to make Classic ASP and ASP.NET 2.0 run on the same IIS (and same WebSite), but eventually we managed to do it (registering and enabling the 32 bit version of the ASP.NET 2.0). A demo of one application was put on the server last week and was working fine, until yesterday when all of a sudden it stopped working (fortunately the Classic ASP application still works) with the following error:  Server Application Unavailable For each attempt to open a *.aspx page, the following entry is added to the application events: Event Id: 1088 Source: ASP.NET 2.0.50727.0 Description: Failed to execute request because the App-Domain could not be created. Error: 0x8007000e Not enough storage is available to complete this operation. The system is not running short nor of RAM neither of disk space. I have monitored the filesystem with Filemon (Sysinternals - Microsoft) and I could not find any "Access Denied" or other suspicious entries so I am excluding issues related to wrong file permissions settings. Fortunately a simple IISRESET sorted the problem but this is obviously only an emergency solution and I need to find the source of the problem as soon as possible. I don't know much about process recycling, application pools, and so on. Therefore I don't know where to start and what kind of information may be helpful so here is a few:  - the application is using impersonation, that is, the worker process is running under the IUSR_server identity;  - some of the queries to our SQL Server db take very long time to come back (minutes) and this is expected. We expect a little number SQL timeouts.  - the application is using Microsoft ASP.NET Ajax 1.0 Beta 2  - the application is not using COM objects (the Classic ASP portion does);  - the web site is protected via SSL. Any help would be immensely appreciated. Thanks, Paolo

  Tags: server application unavailable failed execute request App-Domain could not be created Error 0x8007000e Not enough storage available complete operation

• 01-02-2007, 11:53 PM

  In reply to

  chrisad Joined on 03-06-2004, 1:01 AM Posts 289

  Re: Server Application Unavailable - Failed to execute request because the App-Domain could not be created. Error: 0x8007000e Not enough storage is available to complete this operation. Reply Contact Hey- The error is pretty straight-forward and is basically telling you that the application is running into some memory\disk problems.  In reviewing some of the information you provided, I was distracted by the fact that you said you needed to run ASP.NET 2.0 with the 32-bit switch (SySWoW mode) for the application pool.  Is this absolutely required?  I assume your application is written in x86 and this is necessary but this if possible to re-compile for x64 would be a solid means of helping out here. With all that said, the first thing I would do is isolate, isolate, and isolate more.  You should break down the applications to the barebones level (i.e one app pool for static content only, one for ASP, one for ASP.NET 1.1 (if exist), and one for ASP.NET 2.0) and monitor at this level.  This is very important for helping us to solve the problem without disruption to your other applications. I would then determine where the problem lies.  Keep in mind that ASP.NET might be throwing the error, though the COM objects running in ASP is the source of the memory exhausition.  With a low-level isolation, we can probably figure this out.  I am going to provide you some resources that might can help you a bit - Finding IIS Bottlenecks using Server Performance Advisor 2.0 IIS 6.0 Service Pack 1 Tracing: Inside and Out Configuring IIS for Misbehaving Visual Basic Components Using IIS 6.0 Tracing to Effectively Diagnose Web Server Problems IIS Architecture Overview Hope this helps a bit <g>  Thanks, -Chris ~Chris Former Program Manager IIS Product Unit (Microsoft)

• 03-13-2008, 9:18 AM

  In reply to

  Gregs86 Joined on 03-13-2008, 1:15 PM Posts 1

  Re: Server Application Unavailable - Failed to execute request because the App-Domain could not be created. Error: 0x8007000e Not enough storage is available to complete this operation. Reply Contact Hello, Did you resolve your problem? If yes, can I know how you did please? I have exactly the same problem but I don't find how to resolve it. If I delete temporary asp.net file, it works fine, but not for a long time... And I can't imagine to stop IIS, delete temp and restart IIS every day... Thanks a lot for your answer.

• 05-04-2008, 11:34 PM

  In reply to

  gooriyah Joined on 05-04-2008, 11:13 PM Posts 1

  Re: Server Application Unavailable - Failed to execute request because the App-Domain could not be created. Error: 0x8007000e Not enough storage is available to complete this operation. Reply Contact Hi Paolo, I am having the same problem here and do not have any idea of what is causing this. It seems like there is no shortage of memory or hard disk space but this error message is keep on coming. When I reset iis then it works ok for some time but not for long. I have similar situation as the site was built in ASP originally and new ASP.NET (Framework 2.0) pages are added later. But our server is 32bit so there was no need to do extra steps that you had to make. Also no ASP.NET AJAX framework neither SSL. The ASP.NET pages that we have also do some intensive query to the database to generate report but I do not think this is large enough to cause this kind of problem. If you were able to solve this problem, sharing knowledge will be greatly apreciated.   Thanks, Felix