Getting error "Failed to create file C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\altiris_console\2fc7ab2a\9b76036\-zi_ef3t.out"

Products

• IT Management Suite

Issue/Introduction

When the customer opens the Altiris Console, the following error message appears:

Failed to create file C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\altiris_console\2fc7ab2a\9b76036\-zi_ef3t.out.

Description: An unhandled exception occurred during compilation using the CodeDomProvider 'Microsoft.CSharp.CSharpCodeProvider'. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.ExternalException: Failed to create file C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\altiris_console\2fc7ab2a\9b76036\-zi_ef3t.out.

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:
[ExternalException (0x7f): Failed to create file C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\altiris_console\2fc7ab2a\9b76036\-zi_ef3t.out.]
System.CodeDom.Compiler.Executor.CreateInheritedFile(String file) +212
System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated(IntPtr userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine) +226
System.CodeDom.Compiler.Executor.ExecWaitWithCapture

Cause

This issue is usually caused by missing permissions on the C:\WINDOWS\TEMP directory for some of the default users. Usually GPOs applied to the server can eliminate or block some of the permissions that .NET requires to properly access and write the files needed.

Resolution

1. Verify that there are not GPOs assigned to the server. You can run rsop.msc from the RUN prompt and find out what are the GPOs assigned, if any, to the server. Please refer to MS Article ID: 323276 "How To Install and Use RSoP in Windows Server 2003" (http://support.microsoft.com/kb/323276) if you need assistance of how to use it.

2. Then make sure that the following permissions are set on the C:\Windows\Temp directory. On the Temp folder, Right-click>Properties>Security:
a) Administrators --> Full Control;
b) Power Users --> Modify,Read & Execute, List Folder Content ,Read, Write
c) Everyone --> Read & Execute;
d) Creator Owner --> Full Control (from Special Permissions Only)
e) Network Service --> List Folder/Read Data, Delete;
f) Users --> Transverse Folder/Execute File, Create Files/Write Data, Create Folders/Append Data
g) ASP.NET Machine Account -->Full Control

3. Make sure that .NET is properly registered and installed. Use the following command lines (for more details see Article ID: 27432 "What are the most common commands for registering .NET 1.1.4322?"):
a) regsvr32 "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll"
b) C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -lk 
c) C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -k W3SVC/
d) C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
e) iisreset

4. Open the Altiris Console. You may be prompted to run NSSetup. Go ahead and finish it. Then you should be able to open the Altiris Console properly.

Applies To
Notification Server 6.0.6074 SP3
.NET 1.1 and 2.0
Windows Server 2003