Video Screencast Help

Error: WebClientApiManager

Created: 30 Jan 2013 | 9 comments
chalks's picture

Seeing this in the log after the upgrade to 7.12 MP1.1, doesn't seem to be any mention in the forums:

"31/01/2013 2:13:47 p.m.","WebClientApiManager:ProcessRegister: System.Exception: An exception occurred while executing the request ---> System.Exception: System.Exception: Unable to register the client 971c5e0a-942b-496a-b9e9-72945c86d2d3 ---> 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)","Altiris.TaskManagement.ClientTask.*","w3wp","476"

Can anyone shed some light?

Comments 9 CommentsJump to latest comment

mclemson's picture

Does this happen to all clients?  What computer is referenced by GUID 971c5e0a-942b-496a-b9e9-72945c86d2d3?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner

chalks's picture

In this instance it was a device called 4SWYNDPOSD01 which was available, pingable, etc

Symantec Technical Specialist

EugeneDisc's picture

Hi Chalks.

Any answers to your post yet. I just finished an upgrade to MP1.1 this weekend and I'm seeing a lot of the same errors in my log too.


chalks's picture

Sorry mate, not as yet. There must be others out there seeing the same thing though.

Symantec Technical Specialist

Alex Bizjajev's picture

This exception could occur if "Maximum computers to manage per Task Server" number is exeeded (5000 by default). Please check this value under the Site Services -> Settings -> Task Service -> Task Service Settings. And check if the number of registered clients are exceeded to the corresponding task server.

Thank you,


chalks's picture

I have 2 task servers configured, the CMS and 1 other server. I have configured the CMS to manage a max of 100 active requests whereas the other server has been configured for the max of 5000

Symantec Technical Specialist

chalks's picture

Hi, to answer all the above:

No, it does not happen to all clients

In this instance it was referencing a pc somewhere in the network

I have not found an explaination for this yet

No, the task server max computers does not exceed 5000

No, I do not even have that many devices in this network

Symantec Technical Specialist

dcudney's picture

I am seeing the same error on my install.

Dewayne Cudney

chalks's picture

So this issue is still ongoing. I have a call open with Symantec Support. Apparently, according to the posts I have found about this, this was an issue before the SP release but that it should have been fixed with the updates which have been released. As soon as I have a resolution to this I will update this post.

Symantec Technical Specialist