Solved

ASP.NET 1.1.4322.0 Failed to execute request because the App-Domain could not be created.

Posted on 2004-10-07
6
7,478 Views
Last Modified: 2012-06-21
Windows XP Professional SP2
.NET framework 1.1
.NET SDK
IIS 5.1

I cannot for the life of me get IIS to serve an asp.NET page.  I get the following error:

Server Application Unavailable

The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

The full text of the event log entry is:

Failed to execute request because the App-Domain could not be created. Error: 0x80070002 The system cannot find the file specified.  

Event ID 1088.

This happens every time I try to navigate to a .aspx page.  The server will serve .html and image files just fine.  

So far, I have done the following:

*  Uninstall .net and reinstall
*  Uninstall IIS and reinstall
*  Uninstall both .net and IIS and reinstall first .net then IIS
*  Uninstall both .net and IIS and reinstall first IIS then .net
*  Run aspnet_regiis.exe -i and -r
*  Change permissions in .config to be SYSTEM rather than MACHINE
*  Verify that ASPNET has all necessary permissions (it is now a member of Administrators)
*  Verify that NETWORK has permission to my web root
*  Remove and re-assign web extensions to my root web

This is a new install of IIS, but is running on my workstation.  It has never worked (never meaning today, since that's when I started trying)

I have not yet attempted percussive maintenance, but am quickly heading in that direction.
0
Comment
Question by:eatham111
6 Comments
 
LVL 11

Expert Comment

by:Jokra_the_Barbarian
Comment Utility
0
 

Author Comment

by:eatham111
Comment Utility
I'm not actually running the windows firewall.
0
 
LVL 3

Expert Comment

by:yellowjetski
Comment Utility
This happens when the information store could not be loaded because the distinguished name(DN)of message database /O=org_name/OU=site_name/CN=RECIPIENTS/CN= does not match the DN of directory /O=org_name/OU=site_name/CN=RECIPIENTS/CN=. The database may have been restored to a computer that is in an organization or site different than the original database.

Take a look this link
http://support.microsoft.com/?id=280652

0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 

Author Comment

by:eatham111
Comment Utility
That's for exchange, not ASP.NET
0
 
LVL 3

Expert Comment

by:yellowjetski
Comment Utility
Sorry, This link should help, it has the same problem as you.

http://support.microsoft.com/default.aspx?scid=kb;en-us;315158

Try these steps if the link does not help

This could be a NTFS permission issue. ASP.NET Web applications usually run using the built-in ASPNET account, but occasionally default access permissions are lost. Verify minimum needed permission for ASPNET account to run applications. Refer to section 2 and 3 of Building Secure ASP.NET Applications document.

OR

Your web directory permissions were wrong. In our case we were recieving this error in the event log whenever a particular site try to access any .Net resource.  It turned out the permissions were wrong - i.e. Everyone user needed more access and/or IUSR_COMPUTERNAME needed more access such as READ.
0
 
LVL 14

Accepted Solution

by:
alimu earned 500 total points
Comment Utility
Search through this document for "Minimum Privileges" and "NTFS Permissions" to double-check aspnet account (and your user) isn't denied a required permission.
http://msdn.microsoft.com/webservices/building/security/default.aspx?pull=/library/en-us/dnnetsec/html/SecNetHT01.asp

doublecheck also that your system is at ASP.NET v1.1.    v1.0 is susceptible to an xp only problem due to a weak password on the aspnet account. One of the hotfixes stopped asp.net 1.0 (std on xp professional) starting if it wasn't run under an account with a strong password, this is the workaround: http://support.microsoft.com/?id=827641
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Use System DSN 6 70
Question in regards to SSL and TLS 8 112
State Session High Availibility 2 41
SSRS 2012 URL 11 46
What is an ISAPI filter?   •      It's an assembly (.dll file) that can add or change the way IIS works.   •      They can be enabled globally for your web server or on a site-by-site basis.   When the IIS server receives a request, enabling the ISAPI fi…
Lync server 2013 Backup Service Error ID 4049 – After File Share Migration
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now