IIS - cannot see the aspnet tab - Asked By shah zeb on 08-Oct-11 01:26 AM

If you find following register keys, would you please delete them and

re-register the framework ?

[HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E}\InprocSe

rver32\2.0.XXXX.0]

[HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406F-AB67-2F8B7558F6F6}\InprocSe

rver32\2.0.XXXX.0]

[HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocSe

rver32\2.0.XXXX.0]

The CLR team made changes to the version number which messes with the the setup scripts removal.

From this article

http://weblogs.asp.net/plip/archive/2006/05/25/Where_2700_s-the-ASP.NET-Tab-in-IIS_3F00_-It_2700_s-Missing_2100_-I_2700_ve-installed-.NET-2.0-_2E002E002E00_.aspx

• You are using the 32-bit version of IIS Manager on a 64-bit computer.
• You are using IIS in Microsoft Windows-32-on-Windows-64 (WOW64) mode.
• You have set the Enable32bitAppOnWin64 property to True in IIS. This setting lets IIS run in 32-bit mode on a 64-bit computer.

This tool will run and fix the problem and get the tab to appear properly.  The steps to run this tool are:

1. Close the IIS Management Console (inetmgr) and *any* other open MMCs.
2. Run the asptabtest.vbs. It will check various known issues, correct some of them, and write results to a log file. Use the output to determine whether the issue is resolved, and if not, what steps to take next.
3. Also note that after making any corrective changes to COM/DCOM settings, specifically DCOM security settings, make sure to either terminate (kill) ****ALL**** dllhost.exe processes, OR reboot the computer ****BEFORE**** testing again. Otherwise you may have well 'fixed' the problem, but a latent dllhost will prevent things from working. This is seen consistently when DCOM permissions were the problem.

If its 64bit system then

If you are gong to run IIS 32-bits on WOW64, MMC Support for ASP.Net snap-in is currently not allowed.
We are in the process of writing a KB article to document this.
In general the ASP.net tab is giving you the UI to configure the application to run different versions. You could use the specific version of aspnet_regiis.exe utility to configure this.
The utility is aspnet_regiis -i under C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727, if you want your application to run under 2.0.
There are several command switches to configure specific sites or directory only.
If you see these problems on 32-bit OS there's a known workaround:

• Manually run the install for ASP.NET: ASPNET_regiis -i
• Register the dll for the MMC: regsvr32.exe "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mmcaspext.dll" "rundll32.exe" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\webengine.dll",RegisterAspNetMMC
• From a command prompt run: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\regasm.exe C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\AspNetMmcExt.dll /tlb:AspNetMMCExt.tlb
• Change the About value in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{fedb2179-2335-48f1-aa28-5cda35a2 b36d}" from {7D23CCC6-A390-406F-AB67-2F8B7558F6F7} to {7D23CCC6-A390-406F-AB67-2F8B7558F6F6}