Failing to Upgrade via Symantec Installation Manager (SIM): Upgrade of database, post install, was not fully successfull.
search cancel

Failing to Upgrade via Symantec Installation Manager (SIM): Upgrade of database, post install, was not fully successfull.

book

Article ID: 162075

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

During the upgrade to SMP 7.6, when the configuration process starts, it fails mid-way saying to review the logs for further details.

Similar errors may be found in the NS logs:

Error 1:
Upgrade of database, post install, was not fully successfull.
Unable to resolve account resource by current user name: Machine\User. When this happens on install or upgrade, it means that user was not created or correctly migrated.
   [Altiris.NS.Exceptions.AeXSecurityException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.Product.CoreSolutionHelper.SetSecurityContextForCurrentUser()
   at Altiris.NS.StandardItems.Product.ProductInstallation.OnInstallProduct(XmlNode installationNode)
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.OnInstallProduct(XmlNode installationNode)
Process: AeXSvc (11384), Thread ID: 40, Module: AeXSVC.exe
Priority: 1, Source: Altiris.NS.Installation.ProductConfigurationWorker.ConfigureProductInternal​

Error 2:
Failed to install the product from the file: C:\Program Files\Altiris\Notification Server\Config\CoreSolution.config
Upgrade of database, post install, was not fully successfull.
   [Altiris.NS.Exceptions.AeXException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.OnInstallProduct(XmlNode installationNode)
   at Altiris.NS.StandardItems.Product.ProductInstallation.InstallProduct()
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.InstallProduct()
   at Altiris.NS.Installation.ProductConfigurationWorker.ConfigureProductInternal(String configFile, Boolean ownsProgressContext, SerializationMode serializationMode)

Unable to resolve account resource by current user name: Machine\User. When this happens on install or upgrade, it means that user was not created or correctly migrated.
   [Altiris.NS.Exceptions.AeXSecurityException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.Product.CoreSolutionHelper.SetSecurityContextForCurrentUser()
   at Altiris.NS.StandardItems.Product.ProductInstallation.OnInstallProduct(XmlNode installationNode)
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.OnInstallProduct(XmlNode installationNode)
Process: AeXSvc (11384), Thread ID: 40, Module: AeXSVC.exe
Priority: 1, Source: Altiris.NS.Installation.ProductConfigurationWorker.ConfigureProductInternal​

Error 3:
Failed to configure: C:\Program Files\Altiris\Notification Server\Config\CoreSolution.config
Upgrade of database, post install, was not fully successfull.
   [Altiris.NS.Exceptions.AeXException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.OnInstallProduct(XmlNode installationNode)
   at Altiris.NS.StandardItems.Product.ProductInstallation.InstallProduct()
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.InstallProduct()
   at Altiris.NS.Installation.ProductConfigurationWorker.ConfigureProductInternal(String configFile, Boolean ownsProgressContext, SerializationMode serializationMode)
   at Altiris.NS.Installation.ProductConfigurationWorker.ConfigureProduct()

Unable to resolve account resource by current user name: Machine\User. When this happens on install or upgrade, it means that user was not created or correctly migrated.
   [Altiris.NS.Exceptions.AeXSecurityException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.Product.CoreSolutionHelper.SetSecurityContextForCurrentUser()
   at Altiris.NS.StandardItems.Product.ProductInstallation.OnInstallProduct(XmlNode installationNode)
   at Altiris.NS.StandardItems.Product.CoreSolutionInstallation.OnInstallProduct(XmlNode installationNode)
Process: AeXSvc (11384), Thread ID: 40, Module: AeXSVC.exe
Priority: 1, Source: Altiris.NS.Installation.ProductConfigurationWorker.ConfigureProductInternal

Cause

Case 1:
This issue is caused when trying to install with an account that is not part of the Symantec Administrators role or without the proper local administrator rights.

Case 2:
In a non-very common scenario, there is the chance that the account domain reference used even when it is the AppID account (primary account used during the inintial installation), in the database this account "domain name" doesn't match exactly with what they are using and what the database has records on:

  1. Running whoami /all from a command prompt, the account domain reference used appears as:
    MyDomain\srvAltiris SID S-1-5-21-1757981266-838170752-839522115-3612
  2. Looking at the database:

select sr.name, st.* from securitytrustee st
left join securityrole sr
on sr.trusteeguid = st.guid
order by trusteeid

We saw that the same account was slightly different:
MyDomain.local\srvAltiris

 

Resolution

For Case 1:
Use the proper user account with the proper rights/privileges. It is not required for SIM (Symantec Installation Manager) to install/upgrade using only the AppID account.  You can use other accounts. It is required that the account used is a Local Admin on the server and a member of the Symantec Administrators role.

For Case 2:

(a) While logged into the server as the Service Account, open a command prompt and run:  whoami /all   This will allow you to see the SID of the user.

Example output: 

User Name      SID

============== =============================================

epm\smpservice S-1-5-21-920593274-1845912902-1984839303-1111

(b) Copy the SID returned by the previous command and paste it into the "@sid" variable of the following query, then run it against the database using SQL Management Studio.

declare @sid nvarchar(64)

set @sid = 'S-1-5-21-920593274-1845912902-1984839303-1111'

 

select st.Name as [Account Name], rk.KeyValue as [SID], st.Guid, sr.Name as [Role Membership]

from securitytrustee st

join vItem i on i.Name = st.Name and i.ClassGuid = 'ADE25CE3-55D9-4E6B-BCE3-129C725E16C4'

join ResourceKey rk on rk.ResourceGuid = i.Guid and rk.KeyName = 'sid'

left join ResourceAssociation ra on ra.ChildResourceGuid = st.Guid

  and ra.ResourceAssociationTypeGuid = '63468F04-6751-448D-891C-B59906360A27' -- Role Trustee

left join SecurityRole sr on sr.Guid = ra.ParentResourceGuid

where rk.KeyValue = @sid

order by 1

 

Usually the error in the SMP logs is caused by the condition where the account name (FQDN) returned from the previous query is incorrect/different than what was returned by “whoami /all”.

Therefore it must be renamed to the correct name in order for the upgrade to work during database configuration time.

For example: Suppose the previous query returned the account name "smpService.emp.graniteLabs.us"; but the correct name (returned by whoami /all) was “epm\smpService”

(c) Once the correct SID and domain\name of the user are known, set them respectively (lines 6 & 7) of the SQL script attached to this article, and run it against the database:

Note: It is always good practice to backup the database before running scripts that modify tables.

Attachments

change name of service account.sql get_app
Powered by Wolken Software