App-Domain could not be created. Error: 0x80131902

re: App-Domain could not be created. Error: 0x80131902

ramseur — Fri, 10 Mar 2006 16:41:11 GMT

You dont have to do all that to fix it. A simple recompile fixes it for me. Sometimes I think app_domains get corrupted and you get a kick out error. I dont have to uninstall anything to get it to work...just a simple recompile.

re: App-Domain could not be created. Error: 0x80131902

Jonathan — Fri, 10 Mar 2006 20:20:24 GMT

Well, what about a user who is only using the website, so he hasn't compiled, and is not going to compile anything, perhaps does not even have visual studio or any tools to compile.
Think about a user who download the rainbow web site to use ( most users will fall into this category i think ). and he goes to use the site and catched that errror.
I afree recompile is the easiest fix... but it's nice to know there is a workaround when comiling is not an option.

re: App-Domain could not be created. Error: 0x80131902

rob — Sun, 27 Aug 2006 06:23:19 GMT

Exactly my situation - not wanting to recompile - worked for me - many thanks. Note: aspnet_regiis.exe lives in subdirectory of that given above (subdirectory has name of framework version - choose the one you are running).

re: App-Domain could not be created. Error: 0x80131902

barnard_rob — Tue, 21 Nov 2006 05:07:53 GMT

Jonathan,

Thank you Jonathan and Mike, the fix works.

I tried recompiling and all to no avail. One difference between Mike Stone's configuration and mine is I still had v1.1 of ASP.NET (along with v2); had to drill farther down the path to find & execute aspnet_regiis.exe. Running the version 2 of aspnet_regiis.exe removed everything.

The application is working well now. Thanks.

Rob
USA, Michigan

the rasx() context » Blog Archive » Today???s Software Development Links

the rasx() context » Blog Archive » Today???s Software Development Links — Tue, 12 Jun 2007 17:27:39 GMT

PingBack from http://www.kintespace.com/rasxlog/?p=652

CrossRoads

CrossRoads — Fri, 21 Sep 2007 02:58:58 GMT

PingBack from http://paanis.wordpress.com/2007/09/21/47/

Quarter to Twelve » Blog Archive » App-Domain could not be created. Error: 0×80131902

Mon, 11 Feb 2008 21:15:27 GMT

PingBack from http://blog.halftonetech.com/2008/02/11/app-domain-could-not-be-created-error-0x80131902/

re: App-Domain could not be created. Error: 0x80131902

vainternet — Thu, 14 Feb 2008 11:05:36 GMT

give access to the ASPNET and IIS_WPG account names to the directory by right clicking on the directory, properties > security > add

re: App-Domain could not be created. Error: 0x80131902

swexpert — Fri, 23 May 2008 13:42:10 GMT

Hi,

Adding to those comments of domenica and Rob, I'd like to add again that aspnet_regiis.exe is not within the system path.

So one has to goto

C:\Windows\Microsoft.NET\Framework\{Framework Version} Instead of C:\Windows\Microsoft.NET\ as mention in Jonathan's steps

{{In my case it was C:\Windows\Microsoft.NET\Framework\v2.0.50727 despite the fact that I had versions 1 and 1.1 installed as well. }}

Secondly trying to replicate the error, I observed that before fixing the error using the above listed method by Jonathan, the control seemed to be going straight to .Net and not via IIS, causing the error. In other words. Just stop the w3s service and it will start behaving weird again...stop the service, open a non-existent page ../something.aspx and it will keep on showing the earlier page (from cache maybe?).

Thanks Jonathan.

Regds

Inderjeet

re: App-Domain could not be created. Error: 0x80131902

CD Rates — Wed, 09 Dec 2009 17:58:45 GMT

thanks, this cleared this right up