ASP.NET 2.0 web app will not run in IIS 5.0

Also on the properties on your virtual directory make sure you have clicked the button to turn your virtual directory into an application.

Open IIS Manager, select your website, navigate to your virtual directory, right click on it and select properties, then choose the Virtual Directory tab and click the create button next to the application name box. Apply, then OK.

Have a look at the following website it has a list of steps for setting up virtual directories

http://www.hkvstore.com/aspnetmaker/doc/aspnet2primer.htm

Here is the Virtual Directory properties with the application name and button highlighted.

from

http://www.hkvstore.com/aspnetmaker/doc/aspnet2primer.htm

Herein lies the problem -- all of the screen shots above are for IIS 6.0 -- I am on IIS 5.0 [See screen shot below]. I have poked and prodded my way through IIS without success. There is no ASP.NET tab as we are all familiar with in IIS 6.0.

I thought maybe I needed to add some code to my web.config or something since there is no ASP.NET tab to use.

Thanks,
Jason

OK -- I think asp.net 2.0 is registered in this IIS server [so is 1.0 and 1,1]. I believe this to be true because the .Net Framework 2.0 and ASP.NET Version 2.0 are referenced in this forced error message listed below.

Note: the application that generated the error message listed below runs fine on this iis server -- i forced this error message so as to demonstrate that ASP.NET 2.0 is in fact registered on this iis server 5.0.

[look at the last line]

If you compare this error message with the first one i posted -- each references a different asp.net version?!?!

Thank you,
Jason

Access is denied. 
Description: An error occurred while accessing the resources required to serve this request. The server may not be configured for access to the requested URL. 
 
Error message 401.2.: Unauthorized: Logon failed due to server configuration.  Verify that you have permission to view this directory or page based on the credentials you supplied and the authentication methods enabled on the Web server.  Contact the Web server's administrator for additional assistance.
 
 
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210 

                                              

1:
2:
3:
4:
5:
6:
7:
8:

In the web.config file of another app on this same iis server i found the following entries. Is it possible that this is what communicates to iis which version of asp.net to use?

I have nothing like this in my web.config.

Thanks,
Jason

<compilation debug="false">
			<assemblies>
				<add assembly="System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
				<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
				<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
				<add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
				<add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
				<add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
			</assemblies>
		</compilation>

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:

Yeah, adding the assemblies to my web.config did not work.

If you have confirmed that the .NET Framework version 2.0 is installed, and run the aspnet_regiis -i in the ..NET Framework version 2.0 folder and the ASP.NET tab is still missing, then download and run the asptabtest.vbs from the following website it will check various known issues, correct some of them, and write results to a log file.

http://blogs.msdn.com/tom/archive/2008/04/17/asp-net-tab-missing.aspx

I found this thread elsewhere -- maybe this is what needs to be done? Thoughts?

http://forums.iis.net/t/621103.aspx

It references something that carl_tawn: suggested of using "aspnet_regiis -i" but instead using "aspnet_regiis -c"

This is a road i have never been down.
The web app that spits out that error message above that references the asp.net 2.0 is actually from a "Directory" in IIS -- not a "Virtual Directory" as i have created for the new app that wont run.

Any thoughts?

Ok wolfman007 -- when i return from lunch i will investigate your suggestions. thank you.

wolfman007,

Is it your suspicion that IIS 5.0 should also contain an ASP.NET Tab in the properties dialogue box of a site or virtual directory?

I ask only because after reading the posts from the link you recommend it seems like the script can also cause problems on the server and may also require a reboot of the server -- I dont think I am prepared to go through with it with such a risk.

Is there any other way? Let me know your thoughts.

Jason

OK -- Got it all worked out -- thanks for all your help!

Here is the deal:

Following the logic of having to register asp.net versions in iis as mentioned above, i found this thread:
http://www.geekpedia.com/PageView452_AspnetRegiis-Utility.html

Essentially i had to use cmd to run these two commands:
aspnet_regiis.exe -ir
aspnet_regiis.exe -s w3svc/1/root/newassociate
[see the command line data listed below]

Once I registered asp.net with iis the asp.net tabs appeared. I did not have to use the vb script suggested by wolfman007 because the tabs appeared after registration.

Thanks again everybody,
Jason

C:\WINNT\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -ir
Start installing ASP.NET (2.0.50727) without registering the scriptmap.
..............
Finished installing ASP.NET (2.0.50727) without registering the scriptmap.
 
C:\WINNT\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -s w3svc/1/root/
newassociate
Start registering ASP.NET scriptmap (2.0.50727) recursively at w3svc/1/root/newa
ssociate.
Finished registering ASP.NET scriptmap (2.0.50727) recursively at w3svc/1/root/n
ewassociate.

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11: