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.
Hierarchy Node Process failed. Please review the log for details.
Symantec Management Platform 7.5, 7.6, 8.0
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.