Exception trying to access the web site - Unable to validate fully qualified web domain name is current server
search cancel

Exception trying to access the web site - Unable to validate fully qualified web domain name is current server

book

Article ID: 177070

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

When attempting to install Symantec Management Platform (NS 7) Via the Symantec Installation Manager, you are unable to proceed past the screen which asks you to enter the Service Account and FQDN of the server.

The following errors are seen (either on screen or in the logs):

Process: SymantecInstallationManager (3208)
Thread ID: 1
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.UI.NSApplicationIdentityView.ValidateCredentials
Description: Provided credentials (username staff\zaboo) were valid but do not have admin rights.

 ......................................................................

Process: SymantecInstallationManager (3208)
Thread ID: 1
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.UserInfoValidation.ValidateCredentials
Description: Win32 Exception occurred while impersonating user

( Exception Details: System.ComponentModel.Win32Exception: LogonUser returned Win32 Error 997
   at Symantec.Installation.Impersonation.Impersonate(String username, String domain, String password)
   at Symantec.Installation.UserInfoValidation.ValidateCredentials(String Username, String Password, String Domain) )
( 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.UserInfoValidation.ValidateCredentials(String Username, String Password, String Domain)
   at Symantec.Installation.UserInfoValidation.ValidateCredentials(String Username, String Password)
   at Symantec.Installation.UI.NSApplicationIdentityView.ValidateCredentials(String& domainUser)
   at Symantec.Installation.UI.NSApplicationIdentityView.validateFormComplete()
   at Symantec.Installation.UI.NSApplicationIdentityView.winButtonNext_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at Xceed.Editors.WinButton.OnClick(EventArgs e)
   at Xceed.Editors.WinButton.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Xceed.Editors.WinButton.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at Symantec.Installation.UI.MainForm.LaunchWizard(WizardMode wizardMode, Object[] modeParams)
   at Symantec.Installation.UI.MainForm.PerformConditionalWizardLaunch()
   at Symantec.Installation.UI.MainForm._timer_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at Symantec.Installation.SimApplication.LaunchUI(SimConfiguration config, Object[] options)
   at Symantec.Installation.SimApplication.Main(String[] args)
 )
( Extra Details:  Type=System.ComponentModel.Win32Exception Src=SymantecInstallationManager )

Process: SymantecInstallationManager (3208)
Thread ID: 1
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.UI.NSApplicationIdentityView.ValidateCredentials
Description: Provided credentials (username DOMAIN\USER) were not valid.

 ......................................................................

Process: SymantecInstallationManager (3208)
Thread ID: 1
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.UI.NSApplicationIdentityView.ValidateSslCert
Description: Unable to validate fully qualified web domain name is current server

......................................................................

Process: SymantecInstallationManager (3208)
Thread ID: 1
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.UI.NSApplicationIdentityView+IISWebSite.checkWeb
Description: Exception trying to access the web site

( Exception Details: System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
   at System.Net.HttpWebRequest.GetResponse()
   at Symantec.Installation.UI.NSApplicationIdentityView.IISWebSite.checkWeb(String hostname, Boolean ssl, HttpStatusCode& statusCode, NetworkCredential creds, Guid gValidateGuid) )
( 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.UI.NSApplicationIdentityView.IISWebSite.checkWeb(String hostname, Boolean ssl, HttpStatusCode& statusCode, NetworkCredential creds, Guid gValidateGuid)
   at Symantec.Installation.UI.NSApplicationIdentityView.ValidateSslCert()
   at Symantec.Installation.UI.NSApplicationIdentityView.validateFormComplete()
   at Symantec.Installation.UI.NSApplicationIdentityView.winButtonNext_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at Xceed.Editors.WinButton.OnClick(EventArgs e)
   at Xceed.Editors.WinButton.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Xceed.Editors.WinButton.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at Symantec.Installation.UI.MainForm.LaunchWizard(WizardMode wizardMode, Object[] modeParams)
   at Symantec.Installation.UI.MainForm.PerformConditionalWizardLaunch()
   at Symantec.Installation.UI.MainForm._timer_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at Symantec.Installation.SimApplication.LaunchUI(SimConfiguration config, Object[] options)
   at Symantec.Installation.SimApplication.Main(String[] args)
 )
( Extra Details:  Type=System.Net.WebException Src=System )

......................................................................

Source: DCOM
Type: Error
Category: None
Event ID: 10016

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{A9E69610-B80D-11D0-B9B9-00A0C922E750}
 to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20).  This security permission can be modified using the Component Services administrative tool.

......................................................................

Source: W3SVC
Type: Warning
Category: None
Event ID: 1009

A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '1228'. The process exit code was 0xffffffff

Cause

Permissions issue. The user did not have enough access rights.

Resolution

To Resolve this:
  1. Obtain the CLSID that does not allow the user access from the System event viewer (In one case, it was A9E69610-B80D-11D0-B9B9-00A0C922E750 )
  2. Open Regedit
  3. Navigate to HKEY_CLASSES_ROOT\AppID
  4. Do a Find for the CLSID obtained in step 1
  5. There should be a LocalService key in the folder found in step 4. The 'Data' column holds the name that needs permissions change
  6. Open Component Services by accessing Start -> Administrative Tools -> Component Services
  7. Drill-down to Console Root -> Component Services -> Computers -> My Computer -> DCOM Config
  8. In this folder, Right-click and select Properties on the name of service that is not allowing the user access ( In the case detailed in step 1, it was the IIS Admin Service)
  9. Select Security -> Launch and Activiation Permissions Click on the Edit Button.
    1. Compare to the settings on a working NS.
    2. Change to match the settings on the working NS.
            (In the case of the IIS Admin Service, ensure that Administrators have Full "allow" access and Authenticated Users have "allow" access for both Local and Remote activation)
  10. Restart IIS
  11. Restart SIM and retry the installation

Applies To
-Windows Server 2003
-IIS 6.0
-Symantec Installation Manager build 427

Powered by Wolken Software