A critical error occurred: Object moved. Configuration failed while attempting: Pre-Configuring
search cancel

A critical error occurred: Object moved. Configuration failed while attempting: Pre-Configuring

book

Article ID: 173812

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

While installing ITMS on a new server, the Symantec Installation Manager (SIM) fails during the configuration phase of the initial installation and displays the following error message:


Configuration failed.
A critical error occurred:
The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a
hreft="/Altiris/Console/error.htm?aspxerrorpath=/Altiris/NS/Services/NSConfigurationWebService.asmx">here</a>.</h2>
</body></html>
--
Configuration failed while attempting: Pre-Configuring ...

Environment

New installation of ITMS 8.x

Cause

According to the Windows Event logs, there is an issue with access denied to "Temporary ASP.NET Files" folder:

ERROR: CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\altiris_ns\2adb9e0d\e5203314\App_global.asax.77dodr.dll' -- 'Access is denied. '

The following information was included with the event: 

3007
A compilation error has occurred.
2/9/2026 1:15:33 PM
2/9/2026 9:15:33 PM
911f3da6263c4d21b87feaa6cca36ea9
3
1
0
/LM/W3SVC/1/ROOT/Altiris/NS-866-134151453329608067
Full
/Altiris/NS
E:\Program Files\Altiris\Notification Server\Web\
<SMPSERVERNAME>
8056
w3wp.exe
IIS APPPOOL\SMP Server AppPool
HttpCompileException
(0): error CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\altiris_ns\ob133cd4\dbf72da4\App_global.asax.im77dodr.dll' -- 'Access is denied. '
   at System.Web.Compilation.AssemblyBuilder.Compile()
   at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
   at System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp)
   at System.Web.Compilation.BuildManager.CompileGlobalAsax()
   at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
   at System.Web.Compilation.BuildManager.CallAppInitializeMethod()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)


https://smpserver.exemple.com:443/Altiris/NS/Services/LicensingWebService.asmx
/Altiris/NS/Services/LicensingWebService.asmx
10.100.8.19
False
<domain>\<appidaccount>
31
<domain>\<appidaccount>
False
   at System.Web.Compilation.AssemblyBuilder.Compile()
   at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
   at System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp)
   at System.Web.Compilation.BuildManager.CompileGlobalAsax()
   at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
   at System.Web.Compilation.BuildManager.CallAppInitializeMethod()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

 

Resolution

Approach 1:

Make sure the following accounts/groups have permissions under "c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files":

  • CREATOR OWNER
    • Special Permissions > Full Control
  • SYSTEM
    • Full Control
  • Administrators
    • Full Control
  • Users
    • Read & Execute
    • List folder contents
    • Read
  • IIS_IUSRS
    • Modify
    • Read & Execute
    • List folder contents
    • Read
    • Write
  • WMSVC
    • Modify
    • Read & Execute
    • List folder contents
    • Read
    • Write
  • Note: sometimes you may need to add as well "NETWORK SERVICE" and "Authenticated Users" accounts with at least "Read & Execute, List folder contents, and Read"

Delete all Altiris related files in "c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files".

  • To delete the files
    • Stop the Altiris Support Service and Altiris Service
    • Stop IIS (run iisreset /stop in an elevated command prompt).
    • Manually delete all content inside C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files.
    • Restart IIS (iisreset /start).
    • Start the previous Altiris services

Try again the installation. Run a Full Repair  ( SIM → Repair Installed Products → Perform full repair): 

 

Approach 2:

This error typically occurs because the account running your application (usually the IIS App Pool Identity or Network Service) lacks sufficient permissions to write to the ASP.NET temporary compilation folders.

Option1: Grant Permissions to the Temporary Folders

You must ensure the identity running your site has Full Control over two specific directories.Identify your Service Account:
  1. Open IIS Manager, go to Application Pools, and check the Identity of the pool running your site (e.g., ApplicationPoolIdentityNetworkService, or a specific user).
  2. Apply Permissions to C:\Windows\Temp:
    • Right-click C:\Windows\Temp > Properties > Security tab.
    • Click Edit > Add.
    • Enter IIS_IUSRS (the group containing all app pools) or your specific service account name.
    • Check Full Control (or at least Read & Write) and click OK.
    • Restart IIS  (iisreset)
  3. Then run a reconfigure using SIM:
    • Re-run SIM → Repair Installed Products → Reconfigure installed products so IIS applications can be recreated and bound correctly.



 

Option 2: Adjust IIS App Pool Settings

Sometimes Windows won't grant access until a user profile is loaded for the account.
  • In IIS Manager, right-click your SMP Server Application Pool > Advanced Settings.
  • Change the Identity to NetworkService, which often has broader default access than ApplicationPoolIdentity.
  • Alternatively, set Load User Profile to True.
  • Run SIM → Repair Installed Products → Reconfigure installed products and let the configuration process to create the proper references.
  • After the installation is done, place back  ApplicationPoolIdentity as the Identity option.
  • Restart IIS (iisreset)