Support Suite

ASP.NET Tab IIS

If in IIS the tab for ASP.Net does not appear, follow these steps:

1. Verify first that you have the .Net 2.0 Framework installed.  To do this, go to Add or Remove Programs in the Control Panel and verify that you have Microsoft .Net Framework 2  or Microsoft .Net Compact Framework 2.0.  You may also click on Windows Update and find it from there.  If you do not have it, stop IIS, install it, and start IIS (for instructions on stopping and restarting IIS, see # 8-11 below).  Try right clicking on the Web Service virtual directory to see if the tab does not appear.  If this does not resolve the issue, proceed below.

If you installed .Net after installing IIS:

1. Open the command prompt by going to the Start Menu and clicking on Run and the type in cmd.exe.   From here, navigate to (by typing a series of cd .. until you reach the root folder of c: and then you can type cd Windows, cd Microsoft.Net etc. until you reach it.  Alternatively you can type in the full path if your version number matches):

C:\Windows\Microsoft.Net\Framework\v2.0.50727.  Note: the v2.0.50727 is the version number and yours may be different.

1. Once at this directory, type aspnet_regiis.exe –i.   Try right clicking on the WebService Virtual Directory again to see if the tab has appeared.  If that does not fix the issue, continue below.

If you have had other versions of .Net 2.X installed

1. You may have to manually remove any references to other .Net 2.X versions in your registry.  Before doing this, verify that no other applications are trying to any version of .Net prior to 2.0 or any deviation from 2.0.0.     If you are certain that this is the case and you feel comfortable removing these references, proceed below.  If you do not, feel free to contact our support (the info is listed below) and we can connect to your computer remotely and do it for you.
2. Go to Start Menu, then Run and then type in regedit.exe.   Verify for each of the three locations below that none of them contain a reference to any version other than 2.0.0.0.  It is important that there is no number other than zero where XXXX appears in the keys below.  If so, remove those keys from the registry:

[HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E}\InprocServer32\2.0.XXXX.0]
[HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406F-AB67-2F8B7558F6F6}\InprocServer32\2.0.XXXX.0]
[HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer32\2.0.XXXX.0]

1. Again, right click on the WebService Virtual Directory and see if that fixed it.  If it did not, see if one of the conditions below fits your situation.

If you are running IIS on a 64-bit machine

1. Try steps 4 through 6 above.  That should fix it.  If it does not, follow the steps 8-11 below:
2. Stop IIS by going to the command prompt (see step 2 above for instructions to get there) and typing:  iisreset /stop.
3. Navigate to the %systemdrive%\Inetpub\AdminScripts directory.  Type the following command:

Cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 “true”
                Then press ENTER.

1. Note that if your IIS was previously running in 64-bit mode with some 64-bit ISAPI filters then these filters will need to be removed or changed to their 32-bit equivalents before IIS will run properly in 32-bit mode.  For example, if you have ASP.Net 2.0 installed then you’ll need to make sure the ISAPI filter for it points to the 32-bit version of aspnet_filter.dll and not the 64-bit version. 
2. Start IIS again using iisreset /start
3. Again, right click on the WebService Virtual Directory and see if that fixed it.  If it did not, see if one of the conditions below fits your situation.

If you have VMWare Server installed on your machine

1. There are sometimes issues with VMWare conflicting with the ASP.Net tab under Windows Server 2003.  If so, follow the steps below.
2. Stop IIS using iisreset /stop
3. Open the file C:\Windows\System32\inetsrv\MetaBase.xml in Notepad.
4. Search for and see if there is a line that says Enable32BitAppOnWin64=”TRUE”.  If so, delete it.  Save this file.
5. Start IIS again using iisreset /start
6. If that does not work, the utility listed in step 3 aspnet_regiis.exe -i should now work.