During initial installation for CMS7 using SIM 7, the following message occurred: "Configuration failed A critical error occurred: The request failed with HTTP status 401: Unauthorized. Configuration failed while attempting: Configuring services."

Products

• IT Management Suite

Issue/Introduction

Customer tried to install CMS7 using Symantec Installation Manager 7. When the installation is at 50% he gets the following error:

"Configuration failed A critical error occurred: The request failed with HTTP status 401: Unauthorized. Configuration failed while attempting: Configuring services."

 

Cause

Unknown. Possible issues with IIS. Unable to restart some of the services, possibly IIS services.

 

After reviewing SIM installation logs ( Under C:\Documents and Settings\<logged user used during the installation>\Local Settings\Temp\SIM Logs) and looks like there are some issues regarding missing components and not been able to restart IIS services.
1. There is a message saying that the IIS services are running

Priority: 4
Date: 2/25/2009 1:02:46 PM
Tick Count: 1953546
Host Name: Servername
Process: SymantecInstallationManager (1396)
Thread ID: 24
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.ConfigureNS.InsureIISServiceIsRunning
Description: IIS service running.

2. Then SIM tries to stop them, showing the same 'http status 401: unauthorized' entry as your error during installation:

Priority: 1
Date: 2/25/2009 1:02:46 PM
Tick Count: 1953812
Host Name: Servername
Process: SymantecInstallationManager (1396)
Thread ID: 24
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.PerformInstall.InstallProducts
Description: Unable to stop services.

( Exception Details: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Altiris.NS.Installation.ServiceConfigurationWebServiceProxy.GetRegisteredServices()
   at Symantec.Installation.PerformInstall.InstallProducts(Components componentsToInstall) )
( Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.Diagnostics.Logging.EventLog.ReportException(String strMessage, Exception exception)
   at Symantec.Installation.PerformInstall.InstallProducts(Components componentsToInstall)
   at Symantec.Installation.Context.WizardProcess.InstallManager.PerformInstall()
   at Symantec.Installation.InstallTask.ExecuteTask()
   at Symantec.Installation.InstallSessionQueue.ExecuteNextTask()
   at Symantec.Installation.InstallSessionQueue.ExecuteNextTask()
   at Symantec.Installation.Context.WizardProcess.InstallManager.PerformInstallAndConfig()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
 )
( Extra Details:  Type=System.Net.WebException Src=System.Web.Services )

3. Then we get a warning mentioning that there is a config file missing for the TaskServerUpgrade:

Priority: 2
Date: 2/25/2009 1:02:46 PM
Tick Count: 1953921
Host Name: Servername
Process: SymantecInstallationManager (1396)
Thread ID: 24
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.ConfigureNS.CreateTasks
Description: Symantec.Installation.ConfigureNS.CreateTasks: the configuration file C:\Program Files\TaskServerUpgrade\Config\TaskServerUpgrade.config was queued to run but could not be found.

4.Then we get a warning trying initializing a NSConfigurationWebService Url:

Priority: 4
Date: 2/25/2009 1:02:46 PM
Tick Count: 1954640
Host Name: Servername
Process: SymantecInstallationManager (1396)
Thread ID: 24
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.ServicesTask.StartAsync
Description: Initializing NSConfigurationWebService Url: http://IPAddress/Altiris/NS/Services/NSConfigurationWebService.asmx

5. and finally we get the error message that stops apparently the installation:

Priority: 1
Date: 2/25/2009 1:02:46 PM
Tick Count: 1954718
Host Name: Servername
Process: SymantecInstallationManager (1396)
Thread ID: 9
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.ConfigureNS.task_Completed
Description: ConfigureNS - task_Completed(): Configuration Task Configuring services... Failed: The request failed with HTTP status 401: Unauthorized.
( Exception Details: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Altiris.NS.Installation.NSConfigurationWebServiceProxy.EndConfigureServices(IAsyncResult asyncResult)
   at Symantec.Installation.ServicesTask.EndAsync(IAsyncResult result) )
( Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.Diagnostics.Logging.EventLog.ReportException(String strMessage, Exception exception)
   at Symantec.Installation.ConfigureNS.task_Completed(Object sender, CompletedEventArgs e)
   at Symantec.Installation.Task.OnCompleted(Exception ex)
   at Symantec.Installation.ServicesTask.EndAsync(IAsyncResult result)
   at System.Web.Services.Protocols.WebClientAsyncResult.Complete()
   at System.Web.Services.Protocols.WebClientProtocol.ProcessAsyncResponseStreamResult(WebClientAsyncResult client, IAsyncResult asyncResult)
   at System.Web.Services.Protocols.WebClientProtocol.ReadAsyncResponseStream(WebClientAsyncResult client)
   at System.Web.Services.Protocols.WebClientProtocol.ReadAsyncResponse(WebClientAsyncResult client)
   at System.Web.Services.Protocols.WebClientProtocol.GetResponseAsyncCallback(IAsyncResult asyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
   at System.Net.ContextAwareResult.CompleteCallback(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.ContextAwareResult.Complete(IntPtr userToken)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
   at System.Net.HttpWebRequest.ProcessResponse()
   at System.Net.HttpWebRequest.SetResponse(CoreResponseData coreResponseData)
   at System.Net.HttpWebRequest.SetAndOrProcessResponse(Object responseOrException)
   at System.Net.ConnectionReturnResult.SetResponses(ConnectionReturnResult returnResult)
   at System.Net.Connection.ReadComplete(Int32 bytesRead, WebExceptionStatus errorStatus)
   at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
   at System.Net.Connection.ReadCallbackWrapper(IAsyncResult asyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
   at System.Net.ContextAwareResult.Complete(IntPtr userToken)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
   at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
 )
( Extra Details:  Type=System.Net.WebException Src=System.Web.Services )

However, the logs shows that the installation keeps running few more things before it stops.

 

 

Note: This may occur if the IIS service (w3wp.exe), using the Network Service credentials, cannot create files in the .NET 2.0 temporary cache.

If this is the case then, an error will be listed in the Window's Application Event log

Resolution

In this specific installation case, customer mentioned that he is using the IP Address instead of the FQDN, because if he uses the FQDN he gets the message:
"an http connection could not be made to the website you selected"

Customer reinstalled CMS7 after starting from scratch one more time. He mentioned that he still has the same problem (setup hangs at 50%), The setup only continues when he gives in the IP address. Both servername and FQDN are giving an error.
Then the customer tried 2 more things:
a) Specified the IP address of the server on the Networkcard instead of using dhcp
b) Used “localhost” in the field where the FQDN should be during setup
Now the setup finishes successfully.

 

Note: Please check If the issue is due to being able to create files in the .NET temporary folders, see KB: TECH42637 SMP 7.0 installation fails with the error ''Configuration Failed''

 

Applies To
Symantec Management Platform 7.0.3876 + SP1 (a.k.a. NS 7 + SP1)
Symantec Installation Manager 7.0.351