KNOWN ISSUE: Clients Task Agent fail to connect to the Notification Server when the server has hit maximum connections and allow connections to exceed maximum is checked

Article:TECH127373  |  Created: 2010-04-20  |  Updated: 2010-04-20  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


We noticed that that client task agent will try to obtain a count of how many client machines are registered to the task servers that are known for that client machine. Then the client task agent will try to register to the task server with less client registered.  In this case the NS is the one with less registered machines. We see how the client machine tries multiple combinations of servername, FQDN, http and https until it is able to register to the task server. In this scenario, since the NS only allows a max of 100 client tasks to register, then the client machine stays in a limbo state until it is able to connect to a task server. Usually it takes around 15 min to try from one server to another.

Steps to duplicate:
1. Set limit to 100 machines on the Notification Server.
2. Check the option to allow the server to exceed the maximum.
3. Try to connect 105 machines.

The server will reject the clients. The problem is if the NS is to be used as a fail over server it cannot and all the clients go in to an unmanaged state until another site server comes online.

example warning received when exceeded the Max Computer Limit is Exceeded:

Priority: 2
Date: 4/19/2010 7:55:26 PM
Tick Count: 147044515
Host Name: CVGAPP67D
Process: aexnsagent.exe (368)
Thread ID: 2244
Module: client task agent.dll
Source: Client Task Agent
Description: CTaskServerNetCommsConnection::CheckResponseXml(): The task server returned an error: <![CDATA[System.Exception: An exception occurred while executing the request ---> System.Exception: System.Exception: Unable to register the client 9401cfe1-6207-440e-9990-32a9c6c8078b ---> Altiris.ClientTask.Server.Exceptions.ClientTaskServerMaxComputerLimitExceededException: Exception of type 'Altiris.ClientTask.Server.Exceptions.ClientTaskServerMaxComputerLimitExceededException' was thrown.   
at Altiris.ClientTask.Server.RemoteClientTaskManager.GetClientStatusAndLock(AltirisResourceGuid resourceGuid, Boolean ignoreMaxComputerLimit, ClientStatus& client, Boolean& created)    at Altiris.ClientTask.Server.RemoteClientTaskManager.RegisterAndCreateClientRecord(AltirisResourceGuid resourceGuid, String configurationXml, Boolean bLastResort)    at Altiris.ClientTask.Server.ClientTaskServer.RegisterClient(AltirisResourceGuid resourceGuid, Boolean bLastResort, String configurationXml) AtrsLog:Debug    --- End of inner exception stack trace ---   
at Altiris.ClientTask.Server.ClientTaskServer.RegisterClient(AltirisResourceGuid resourceGuid, Boolean bLastResort, String configurationXml)   
at Altiris.ClientTask.Server.ClientTaskServer.ProcessRemoteRegisterClient(Hashtable input, Hashtable& output)   
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingServer.ProcessRequestObject(Object work)    --- End of inner exception stack trace ---   
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequestI(String service, Hashtable input)   
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequest(String service, Hashtable input)   
at Altiris.ClientTask.Server.HttpHandlers.WebClientApiManager.ProcessRegister(XmlTextWriter wr, NameValueCollection queryValues, Stream requestStream, Int32 contentLength)    at Altiris.ClientTask.Server.HttpHandlers.Register.WriteResponse(XmlTextWriter wr)   
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)   
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)]]>


Symantec Management Platform 7.0 SP3, SP4


This is the current behavior with the product.


This issue has been reported to our Symantec Development team. This issue is under review and it may be addressed in a future release.

Supplemental Materials

ValueETK 2013394
DescriptionLogged in Etrack (Symantec) database

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices