(Note: -lk lists all the path of all IIS metabase keys where ASP.NET is scriptmapped, together with the version. Keys that inherit ASP.NET scriptmaps from a parent key will not be displayed.) (Note: The aspnet_regiis.exe utility is an administration utility that manages the installation and uninstallation of multiple versions of ASP.NET on a single computer.)
Run the following command line to remove the all associations to .NET 1.1.4322:
(Note: The -i parameter installs this version of ASP.NET and updates scriptmaps at the IIS metabase root and for all scriptmaps below the root. Existing scriptmaps of lower versions are upgraded to this version.)
Run the following command to restart IIS services:
(Note: It will stop and restart IIS services in order to add the changes into IIS.)
Then the application is finished; test to see if it fixed the installation problem.
If the problem still persists (if you have IIS 6.0):
Go to IIS Manager (Administrative Tools/Internet Information Services (IIS) Manager).
If you have .NET 2.0 installed, go to the Web Sites/Default Web Site and then right-click and select Properties. Click on the ASP.NET tab and, in the "ASP.NET version," select the 1.1.4322 version from the drop list. Click OK.
In the IIS Manager, go to Web Server Extensions and make sure that at least ASP.NET v1.1.4322 is allowed. If both are allowed, then it should not be a problem.
Note: There are cases where in addition to the fix provided in this article, you will need to edit HKLM\Software\Microsoft\ASP.NET\RootVer to read "1.1.4322" before the InstallHelper would let you continue.
Applies To Notification Server 6.0.6074 .NET 2.0*
Imported Document ID: TECH19438
Subscribing will provide email updates when this Article is updated. Login is required.