The following error occurred on the page "WizPage3.aspx"

Products

• IT Management Suite

Issue/Introduction

During the final section of the Notification Server installation (the Notification Server Setup, http://localhost/Altiris/NS/install/nssetup.aspx), you are asked to authenticate at the first page (and the administrator credentials you use are rejected even though those are correct) or an error in the Email settings configuration occurs. This prevents you from completing the installation of the Notification Server.

You may see an error like this:
Could not logon as user "domain\administrator ". Current user is "NT AUTHORITY\NETWORK SERVICE". Token=0, LastError=1326 (Logon failure: unknown user name or bad password).

Cause

Apparently the issue is related to multiple versions of .NET or the current one was not properly installed or privileges assigned to the ASPNET account were limited.

Resolution

Close the window and try to restart NSSetup. If the error is still present you can follow this procedure to fix the problem with ASP.NET.

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.

1. Close the IIS Admin Service by clicking the Start > Control Panel > Administrative Services > Services. Then right-click the IIS Admin Service, and click Stop.
2. On the Notification Server computer, open a command window (Run Command). Use Windows Explorer to go to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 (or equivalent in your environment). Register your aspnet_isapi.dll by dragging it into the command window and adding regsvr32 command on front of the path.
   
   regsvr32 "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll"
   
3. 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.)
   
   C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -lk
   
   (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.)
4. 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)
5. Run the following command line to add the NS Web applications back to .NET 1.1.4322:
   
   C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
   
   (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.)
6. Run the following command to restart IIS services:
   
   iisreset
   
   (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):

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ua
(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.)

Then go back and re-register .NET 1.1 as mentioned on steps 5 and 6 above.

Then, make sure ASP.NET v1.1.4322 is allowed in Web Server Extensions:

1. Go to IIS Manager (Administrative Tools/Internet Information Services (IIS) Manager).
2. In the IIS Manager, go to Web Server Extensions and make sure that at least ASP.NET v1.1.4322 is allowed.

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.

Applies To
Notification Server 6.0, any versions