ASP.NET Tab is missing in the IIS MMC in the web server running Windows XP Pro x64 Edition with .NET Framework 2.0 (WOW64)

 

After installing .NET Framework 2.0 on Windows XP Pro x64 Edition, you don't see the ASP.NET Tab in IIS MMC. This happens if IIS is running in WOW64 mode. In other words, if IIS is running in 32 bit mode on a 64 bit Windows operating system, the ASP.NET tab will not appear in the IIS MMC. This is a known issue.

 

To check whether IIS is configured to run 32 bit applications on 64 bit OS, open the command prompt and navigate to C:\Inetpub\AdminScripts folder and run the following command in the command prompt:

cscript.exe adsutil.vbs get W3SVC/AppPools/Enable32BitAppOnWin64

 

 

WORK AROUND:
===============

1. If you are planning to run only ASP.NET 2.0 applications and not ASP.NET 1.1 applications, don't run IIS in 32 bit mode on a server running 64 bit Windows operating system.

To turn off IIS from running 32 bit applications, run the following command

cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 “false”

2. If you need both ASP.NET 1.1 and 2.0 on 64 bit OS, then you have to enable IIS to run 32 bit applications. In this case the ASP.NET tab will be missing in IIS MMC.

To configure the virtual directories to use specifc ASP.NET versions, you will have to use the command line tool.

aspnet_regiis -s <path of the application>
(Install scriptmaps for this version at the specified path, recursively. Existing
scriptmaps of lower version are upgraded to this version.)
E.g. aspnet_regiis.exe -s W3SVC/1/ROOT/SampleApp1

OR

aspnet_regiis -sn <path of the application>
(Install scriptmaps for this version at the specified path, non-recursively.
Existing scriptmaps of lower version are upgraded to this version.)

 

Thanks,

Pradeep

Comments

  • Anonymous
    March 24, 2008
    Ahhhh, finally an intelligent post! All the other ones I came across just beat arount the issue of switching between 32 and 64 bit IIS modes, and nobody is addressing the bug that you mention. thank you so much!

  • Anonymous
    March 19, 2009
    I just came cross the issue. Thanks Pradeep now I have the answer. I was also wondering why MS is not fixing the issue or have a KB for it.