The node being added to this servers hierarchy matches this server. HierarchyCode:6
search cancel

The node being added to this servers hierarchy matches this server. HierarchyCode:6

book

Article ID: 386318

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

While trying to add a new Child SMP Server to your Hierarchy (under Settings menu, click Notification Server > Hierarchy), you get the following error message:

Hierarchy Node Process failed. Please review the log for details.


The following log entries are noticed in the NS logs on the Parent SMP Server:

 

Entry 1:

Operation started: Executing core task ('AddHierarchyNode' (Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations : AddNode_Synchronous(HierarchyNode, Hashtable):Guid)) ...
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:41 PM, Tick Count: 1479059828 (17.02:50:59.8280000), Size: 409 B
Process: AeXSvc (5264), Thread ID: 145, Module: Altiris.NS.dll
Priority: 16, Source: CoreTaskServiceThread

Entry 2:

Operation completed: Starting task ('Add a Hierarchy Node Asynchonously' (AddHierarchyNode @ 9a69d236-7d17-42a4-8ad3-386147d9e5d3, Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.AddNode_Synchronous)), total time=0:00:00.07
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:41 PM, Tick Count: 1479059828 (17.02:50:59.8280000), Size: 467 B
Process: AeXSvc (5264), Thread ID: 147, Module: Altiris.NS.dll
Priority: 16, Source: CoreTaskManagerService

Entry 3:

Operation started: Updating forward servers (1) ...
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:41 PM, Tick Count: 1479060296 (17.02:51:00.2960000), Size: 269 B
Process: AeXSvc (5264), Thread ID: 145, Module: Altiris.NS.dll
Priority: 8, Source: ForwardServers

Entry 4:

Operation completed: Updating forward servers (1), servers=1, updated=1, total time=0:00:00.06
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:41 PM, Tick Count: 1479060359 (17.02:51:00.3590000), Size: 312 B
Process: AeXSvc (5264), Thread ID: 145, Module: Altiris.NS.dll
Priority: 8, Source: ForwardServers

Entry 5:

Skip KMS transfer because hash is the same: local[tQ0RYCCNbgZ8vbv9EiphTFaQBPo84PausxWyJOf0HRw=], remote[tQ0RYCCNbgZ8vbv9EiphTFaQBPo84PausxWyJOf0HRw=]
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:42 PM, Tick Count: 1479061203 (17.02:51:01.2030000), Size: 401 B
Process: AeXSvc (5264), Thread ID: 145, Module: Altiris.NS.Replication.dll
Priority: 8, Source: ReplicationJobHelper.TransferKMSKeys

Entry 6:

Hierarchy Node process exception. 

The node being added to this servers hierarchy matches this server. HierarchyCode:6 ---> The node being added to this servers hierarchy matches this server. HierarchyCode:6
   [SoapException @ System.Web.Services.dll]
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage, WebResponse, Stream, bool)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(string, object[])
   at Altiris.NS.Replication.Hierarchy.HierarchyNodeManager.CreateRelationship(HierarchyNode, TaskProgressEventHandler)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.HierarchyNodeProcess(HierarchyNode, HierarchyStructureChangeEventReason, bool)

SOAP Exception detail:Unable to add the specified node to the hierarchy. The node being added to this servers hierarchy matches this server. HierarchyCode:6

Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(int, string, string, Exception, string)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.HierarchyNodeProcess(HierarchyNode, HierarchyStructureChangeEventReason, bool)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.AddNode_Synchronous(HierarchyNode, Hashtable)
   at System.RuntimeMethodHandle.InvokeMethod(object, object[], Signature, bool)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(object, object[], object[])
   at System.Reflection.RuntimeMethodInfo.Invoke(object, BindingFlags, Binder, object[], CultureInfo)
   at Altiris.NS.TaskManagement.TaskThread.Execute(TaskManagerServiceArgs, ProgressContext)
   at Altiris.NS.TaskManagement.CoreTaskServiceThreadBase<,>.ExecuteThreadProc(object)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext, ContextCallback, object, bool)
   at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, object, bool)
   at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, object)
   at System.Threading.ThreadHelper.ThreadStart(object)

-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:42 PM, Tick Count: 1479061250 (17.02:51:01.2500000), Size: 2.33 KB
Process: AeXSvc (5264), Thread ID: 145, Module: System.Web.Services.dll
Priority: 1, Source: SoapHttpClientProtocol.ReadResponse

Entry 7:

Hierarchy Node creation failed. 
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:42 PM, Tick Count: 1479061250 (17.02:51:01.2500000), Size: 309 B
Process: AeXSvc (5264), Thread ID: 145, Module: Altiris.NS.Replication.Hierarchy.dll
Priority: 4, Source: AsynchronousHierarchyOperations.AddNode_Synchronous

Entry 8:

Hierarchy Node process exception occured after 3 times attempts. 

The node being added to this servers hierarchy matches this server. HierarchyCode:6 ---> The node being added to this servers hierarchy matches this server. HierarchyCode:6
   [SoapException @ System.Web.Services.dll]
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage, WebResponse, Stream, bool)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(string, object[])
   at Altiris.NS.Replication.Hierarchy.HierarchyNodeManager.CreateRelationship(HierarchyNode, TaskProgressEventHandler)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.HierarchyNodeProcess(HierarchyNode, HierarchyStructureChangeEventReason, bool)

SOAP Exception detail:Unable to add the specified node to the hierarchy. The node being added to this servers hierarchy matches this server. HierarchyCode:6

Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(int, string, string, Exception, string)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.HierarchyNodeProcess(HierarchyNode, HierarchyStructureChangeEventReason, bool)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.AddNode_Synchronous(HierarchyNode, Hashtable)
   at System.RuntimeMethodHandle.InvokeMethod(object, object[], Signature, bool)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(object, object[], object[])
   at System.Reflection.RuntimeMethodInfo.Invoke(object, BindingFlags, Binder, object[], CultureInfo)
   at Altiris.NS.TaskManagement.TaskThread.Execute(TaskManagerServiceArgs, ProgressContext)
   at Altiris.NS.TaskManagement.CoreTaskServiceThreadBase<,>.ExecuteThreadProc(object)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext, ContextCallback, object, bool)
   at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, object, bool)
   at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, object)
   at System.Threading.ThreadHelper.ThreadStart(object)

-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:42 PM, Tick Count: 1479061546 (17.02:51:01.5460000), Size: 2.36 KB
Process: AeXSvc (5264), Thread ID: 145, Module: System.Web.Services.dll
Priority: 1, Source: SoapHttpClientProtocol.ReadResponse

Entry 9:

Failed to execute task: 'AddHierarchyNode' (Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations : AddNode_Synchronous(HierarchyNode, Hashtable):Guid)

The node being added to this servers hierarchy matches this server. HierarchyCode:6 ---> The node being added to this servers hierarchy matches this server. HierarchyCode:6
   [SoapException @ System.Web.Services.dll]
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage, WebResponse, Stream, bool)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(string, object[])
   at Altiris.NS.Replication.Hierarchy.HierarchyNodeManager.CreateRelationship(HierarchyNode, TaskProgressEventHandler)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.HierarchyNodeProcess(HierarchyNode, HierarchyStructureChangeEventReason, bool)
   at Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.AddNode_Synchronous(HierarchyNode, Hashtable)

SOAP Exception detail:Unable to add the specified node to the hierarchy. The node being added to this servers hierarchy matches this server. HierarchyCode:6

Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(int, string, string, Exception, string)
   at Altiris.NS.TaskManagement.CoreTaskServiceThreadBase<,>.ExecuteThreadProc(object)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext, ContextCallback, object, bool)
   at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, object, bool)
   at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, object)
   at System.Threading.ThreadHelper.ThreadStart(object)

-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:42 PM, Tick Count: 1479061593 (17.02:51:01.5930000), Size: 1.95 KB
Process: AeXSvc (5264), Thread ID: 145, Module: System.Web.Services.dll
Priority: 1, Source: SoapHttpClientProtocol.ReadResponse

Entry 10:

Operation completed: Executing core task ('AddHierarchyNode' (Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations : AddNode_Synchronous(HierarchyNode, Hashtable):Guid)), total time=0:00:01.76
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:42 PM, Tick Count: 1479061593 (17.02:51:01.5930000), Size: 430 B
Process: AeXSvc (5264), Thread ID: 145, Module: Altiris.NS.dll
Priority: 16, Source: CoreTaskServiceThread

 

Main error entry:

The node being added to this servers hierarchy matches this server. HierarchyCode:6 ---> The node being added to this servers hierarchy matches this server. HierarchyCode:6

The node being added to this servers hierarchy matches this server. HierarchyCode:6 ---> The node being added to this servers hierarchy matches this server. HierarchyCode:6
   [SoapException]

Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(int, string, string, Exception, string)
   at Altiris.NS.UI.Admin.Configuration.Hierarchy.HierarchyOperations.GetAsynchronousNodeOperationPercentage(string)
   at System.RuntimeMethodHandle.InvokeMethod(object, object[], Signature, bool)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(object, object[], object[])
   at System.Reflection.RuntimeMethodInfo.Invoke(object, BindingFlags, Binder, object[], CultureInfo)
   at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(object, object[])
   at System.Web.Services.Protocols.WebServiceHandler.Invoke()
   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
   at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext)
   at System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep, ref bool)
   at System.Web.HttpApplication+PipelineStepManager.ResumeSteps(Exception)
   at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext, AsyncCallback)
   at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest, HttpContext)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, int)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, int)
   at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, ref RequestNotificationStatus)
   at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, ref RequestNotificationStatus)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, int)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, int)

HTTP [POST]: http://parentSMP.example.com/Altiris/NS/Admin/Configuration/Hierarchy/HierarchyOperations.asmx
 ip: [10.0.17.74]; languages: [en-US,en;q=0.9]; content-length: [401];
 timings: [[R] 00:00:00.0305077(W: 00:00:00.1756850)];
 response: [200 OK]; x-smp-nsversion: [8.7.4327.0];
-----------------------------------------------------------------------------------------------------
Date: 1/3/2025 3:08:44 PM, Tick Count: 1479063109 (17.02:51:03.1090000), Size: 2.90 KB
Process: w3wp (7048), Thread ID: 345, Module: Altiris.Web.NS.dll
Priority: 1, Source: HierarchyOperations.GetAsynchronousNodeOperationPercentage

Environment

ITMS 8.x, 8.7.x

Cause

Two possible reasons:

  1. Sharing the same database between both SMP Servers, which is not supported and a bad practice.
  2. Having the Child SMP Server Communication profile as the primary Agent Communication Profile on the Parent SMP Server Console instead of the Parent SMP Server itself (because it was exported from the Child SMP Server and imported into Parent SMP Server)

Resolution

Scenario 1:

Make sure you are not sharing the same database (meaning, that there is the same database been accessed for both SMP Servers at the same time). Check under Settings>All Settings>Notification Server>Database Settings on both servers. If you do, then you will need to create a new database for your Child SMP Server.

 

Scenario 2:

You may need to delete both NS Communication profiles and let the Parent SMP Server recreate a new one for itself.
See KB 277429 "Duplicate Task Server communication profiles show Existing profile '' contains the same FQDN and web application path" for steps on how to delete both NS Communication Profiles.
After both NS Communication profiles are gone, after refreshing the page, the Parent SMP Server Communication Profile should have been re-created automatically. If not, thy this:

  1. In the Parent SMP Console, on the "Symantec management Agent Communication Profiles" folder (Settings>All Settings>Agents/Plug-ins>Symantec Management Agent),  right-click and create New NS Communication profile.  This will create a new default communication profile.
    NOTE: The default communication profile will have a computer monitor and a little yellow badge.   Cloned profile icons will not have a yellow badge.

Note:  If you right-click on the Symantec management Agent Communication Profiles folder and only see the option for "New Profile" and not the option for "Create NS Profile" check the following: 
In the coresettings.config (C:/Program Data/Symantec>SMP>Settings) file look for the  <customSetting key="NSCommunicationProfileGuid" type="local" value="d8fb9513-dc66-4a23-87b3-2f3499c1fede" /> . 
Remove the GUID from the value field:
<customSetting key="NSCommunicationProfileGuid" type="local" value="" />. 
Stop and restart the Altiris service. 
Go back to the Symantec management Agent Communication Profiles folder and right-click on it.  You should see the option for "Create NS Profile".  

 

 

Powered by Wolken Software