If .NET 1.1.4322 is not registered properly, or if I am not sure if it is installed properly, what commands can I use in order to register it on my Notification Server? Or if .NET 2.0 is installed, how I make sure that .NET 1.1.4322 is also registered on my system?
Here are the steps to follow:
Reset ASP.NET settings
Note: Resetting the ASP.NET settings is quick and won't adversely affect your Notification Server. It often helps correct authentication problems in the Notification Server.
- Close the IIS Admin Service by clicking the Start > Control Panel > Administrative Services > Services. Then right-click the IIS Admin Service, and click Stop.
Run the following command line to view the NS Web applications associated to .NET 1.1.4322: (Note: Run the following commands from the RUN prompt or from the C prompt.)
(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:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -k W3SVC/
(Note: -k <path> removes all scriptmaps to any version of ASP.NET from the specified path, recursively. E.g. aspnet_regiis.exe -k W3SVC/1/ROOT/SampleApp1)
Warning: If you have any other application under the W3SVC root that uses a different .NET version, the command above will overwrite it and set it to the 1.1.4322. You can run the command above and just go back to those directories and change back to the desired .NET version under the ASP.NET tab in the right-click>properties.
- Run the following command line to add the NS Web applications back 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.
Note: In case that you want to remove .NET 2.0 from being used by IIS without removing it from Add/Remove Programs, you can try the following command line (just make sure that you are unistalling the right version of .NET):
(Note: the -u switch formerly listed for this command removes .NET 2.0 from being used by IIS and then associates unregisterred applications to the highest installed version of .NET which would still be 2.0. By using -ua, it only removes the registrations.)
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 HK-LM\Software\Microsoft\ASP.NET\RootVer to read "1.1.4322" before the InstallHelper would let you continue.