Attempts to make changes to the hierarchy configuration for a specific child result in an error as well as failures in the replication process.
Error: Hierarchy Node Process failed. Please review the log for details.
The logs contain an error similar to the following excerpt:
Description: Failed to execute task: 'EditHierarchyNode' (Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations : UpdateNode_Synchronous(Altiris.NS.Replication.Hierarchy.HierarchyNode):Void)
The node being verified on the local server was not found. This server should have reference to a parent node with server name SMP-T1.Gamegrid.local. HierarchyCode:2 ---> The node being verified on the local server was not found. This server should have reference to a parent node with server name SMP-T1.Gamegrid.local. HierarchyCode:2
[System.Web.Services.Protocols.SoapException @ System.Web.Services] 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.Replication.Hierarchy.HierarchyNodeManager.ModifyRelationship(HierarchyNode node, TaskProgressEventHandler progress) at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.HierarchyNodeProcess(HierarchyNode node, HierarchyStructureChangeEventReason processMode, Boolean catchException) at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.UpdateNode_Synchronous(HierarchyNode node)
An examination of the hierarchy configuration from within the console showed that the server name was correct, but the server URL was incorrect. It had the parent server’s name or another instead of the correct name for the child it is configured for.
Symantec Management Platform 7.5, 7.6, 8.0
Hierarchy Node Process failed. Please review the log for details.
Unknown. In a couple of reported cases it occurred after an upgrade from an earlier version of SMP.
Attached to this article are two SQL modification queries. Use one or the other depending on if the problem is with a child URL in the parent’s database; or if the problem is with the parent URL in a child server’s database.
ChangeChildServerURL.sql : Run against the parent’s database to modify one or more child URLs.
ChangeParentServerURL.sql: Run against a child’s database to modify the parent’s URL
Usage: As with all SQL scripts that externally modify the database it is recommended that a current backup of the database exist before proceeding.
On line 7 where it sets the @serverName variable type in the name of the child or parent server exactly as it is displayed in the console UI.
If you are not sure run the following query against the database to find out the correct name: select i.Name as Parent, i2.Name as Child, CAST(i3.state as xml) HiearchyNodeState, i3.Guid as HierarchyNodeGuid from HierarchyNode hn join Item i on i.Guid = hn.ParentGuid join Item i2 on i2.Guid = hn.ChildGuid join Item i3 on i3.Guid = hn.ItemGuid order by 2
On line 8 enter in the correct name of the server ONLY if it is different than the name entered on line 7
On line 13 where @correctURLname is automatically set—if https is being used instead of http then add an “s” onto the “http” tag.
Run the query against the parent’s database
Perform the following steps to resolve the problem. This will require having access to SQL Management Studio to query the database and make modifications.