Failed to perform re-register. Error response returned from server: The handler 'RegisterTaskServer' is failed to process request.

book

Article ID: 171791

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server) Task Server

Issue/Introduction

  • Installed Client Task Server.
  • After the installation completes, in the SMP Console the Task Service is grayed out. 

The Agent logs on the desired Task Server shows the following

Failed to perform re-register.
Error response returned from server: The handler 'RegisterTaskServer' is failed to process request. Computer a3054702-6c60-4e6d-a702-85aab6311b8d trying to register as a task server (version: 8.1.5860) on NS da04b406-b2ac-4d26-9807-63cf13d2d16a is not registered as a site server on NS. It may be temporary situation until collections update on the NS is performed. Please make sure that this computer is registered on NS as site server. In case of disaster recovery scenario, run 'NS.Restore Task Servers' Windows Schedule.

Message 1:

Task Server a3054702-6c60-4e6d-a702-85aab6311b8d (version: 8.1.5860) is registering on NS...
-----------------------------------------------------------------------------------------------------
Date: 5/30/2018 1:04:16 PM, Tick Count: 8882015 (02:28:02.0150000), Size: 325 B
Process: AtrsHost.exe (6956), Thread ID: 8640, Module: AtrsHost.exe
Priority: 4, Source: ClientTaskServer

Message 2:

Failed to perform re-register.
Error response returned from server: The handler 'RegisterTaskServer' is failed to process request. Computer a3054702-6c60-4e6d-a702-85aab6311b8d trying to register as a task server (version: 8.1.5860) on NS da04b406-b2ac-4d26-9807-63cf13d2d16a is not registered as a site server on NS. It may be temporary situation until collections update on the NS is performed. Please make sure that this computer is registered on NS as site server. In case of disaster recovery scenario, run 'NS.Restore Task Servers' Windows Schedule.Request: source=172.23.33.81, version=<legacy>, size=0, page=RegisterTaskServer.aspx
   [System.Exception @ Altiris.ClientTask.Server]
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.CheckResponseForFailure(WebResponse webResp, Stream respStream, StreamReader respStreamRdr, XmlTextReader respXmlTxtRdr)
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.PostToNotificationServer(String url, NSWebConnectionBuildRequestStreamDelegate requestStreamDelegate, Stream& respStream, StreamReader& streamRdr, XmlTextReader& xmlTxtRdr, Boolean& dataEncryped, Int32 nMaxAttempts, Int32 nTimeout)
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.RegisterTaskServer(Guid serverGuid, Guid resourceGuid, String version, Int32 build, Nullable`1 httpPort, Nullable`1 httpsPort, TaskServerConfiguration& tsConfig)
   at Altiris.ClientTask.Server.ClientTaskServer.RegisterTaskServer(Version taskServerVersion)
   at Altiris.ClientTask.Server.ClientTaskServer.ReRegister(Version taskServerVersion)

Exception logged from:
   at Altiris.DotNetLib.Logging.AtrsLog.ExceptionMessage(String message, Exception exception)
   at Altiris.ClientTask.Server.Logging.NSAgentLog.ReportMessage(Severity severity, String moduleName, String source, Exception exception, String message, Object[] arguments)
   at Altiris.ClientTask.Server.ClientTaskServer.ReRegister(Version taskServerVersion)
   at Altiris.ClientTask.Server.ClientTaskServer.ProcessRegistrationThreadProc()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
-----------------------------------------------------------------------------------------------------
Date: 5/30/2018 1:04:16 PM, Tick Count: 8882046 (02:28:02.0460000), Size: 2.77 KB
Process: AtrsHost.exe (6956), Thread ID: 8640, Module: AtrsHost.exe
Priority: 1, Source: Altiris.ClientTask.Server.ClientTaskServer.ReRegister
 

Cause

There are some internal checks that were not run in the proper order for the task service assignment.

Environment

ITMS 8.1 and later

Resolution

  1. Verify that sending Basic inventory from the affected Task Server and Notification Server is successful and NSE is processed.
  2. On the SMP server:
    1. Run 'NS.Restore Task Servers' fon Windows Task Scheduler.
      Note: There are different scenarios when Task Server might already exist but not configured on SMP as a Site Server. "NS.Restore Task Servers" scheduled task adds all installed Task Servers into NS Site Server collection if they are not there. Also, after Symantec Management Agent with newly installed Task Services sends its inventory to SMP, this remote Task Server might be added into the Site Server collection on SMP by executing Windows schedule "NS.Restore Task Servers"
    2. Perform Full membership update from the console (Settings > Notification Server > Resource Membership Update)
    3. Restart "Altiris Client Task Data Loader" and "Altiris Object Host Service" services