Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\altiris_ns\d25f06e1\98ee6a1c\hash.web" is denied

Products

• IT Management Suite

Issue/Introduction

After installing or running a repair on Notification Server, customer gets the following error when he tries to open the Altiris Console:

Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\altiris_ns\d25f06e1\98ee6a1c\hash.web" is denied

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Cause

Possible corruption on .NET files or missing permissions on file.

Resolution

In order to solve this problem we need to reset the ASP.NET settings. Also it is suggested to check the permissions on the file which access is denied. ASP.NET Machine Account (<server name>\ASPNET) should have full permissions. The actual error message suggests some steps that you should follow before doing the following:

Reset ASP.NET settings

Note: resetting the aspnet 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.

If the problem still persists (if you have IIS 6.0):

1. Go to IIS Manager (Administrative Tools/Internet Information Services (IIS) Manager).
2. 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.
3. 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.

 

 

Applies To

NS 6.0.xxxx