Client Management Suite

I've been having some problems pushing out patches so I started monitoring the Agent logs and noticed the following failure appear quite often on several computers:

<event date="09/22/2015 15:16:07.4060000 -04:00" severity="2" hostName="COMPUTER7" source="Client Task Agent" module="client task agent.dll" process="AeXNSAgent.exe" pid="10000" thread="6096" tickCount="1142889314"><![CDATA[Could not register using "https://AltirisServer.Domain.com:443/Altiris/ClientTaskServer/Register.aspx"]]></event>

From here I checked the ClientTaskServer application in IIS and found that the physial path \Program Files\Altiris\Altiris Agent\Client Task Server\ServerWeb is missing the Register.aspx file mentioned in the event above.

Am I wrong in assuming the file should be there, and if I'm not how do I go about getting it back? I've also been seeing the below failure message that makes it sound like the Register.aspx file is in fact missing:

<event date="09/22/2015 15:16:07.4140000 -04:00" severity="1" hostName="COMPUTER7" source="NetworkOperation" module="AeXNetComms.dll" process="AeXNSAgent.exe" pid="10000" thread="6096" tickCount="1142889314"><![CDATA[Operation 'Head' failed. 
Protocol: HTTP 
Host: AltirisServer.Domain.com:80 
Path: /Altiris/ClientTaskServer/Register.aspx 
Http status: 403 
Id: {0EAFBA10-92F2-4BBF-89C7-9574D70F8A07} 
Error type: HTTP error 
Error result: 0x80042D21 
Error code: 0 
Error note: HTTP status: 403 Forbidden. Empty response content received, the remote web server is down or URL is invalid 
Error message: HTTP error occured]]></event>

Is this the TS on the SMP or a TS on a SS? 

Have you tried repairing TS via ARP?

Hi,

Register.aspx does not exist as a real file, it is (basically) function described in config and implemented in Altiris.ClientTask.Server.Web.dll. Please check status of "Altiris Object Host Service" and "Altiris Client Task Data Loader" services: they should be in running state. You may also check status of this task server on a site-servers page (NS Console -> Site Server Settings; expand Site Management, locate and select node with corresponding task server) - if status of the Task Server is "green" and you see active clients assigned to such TS then, most probably, this is not the task server problem. I suggest to check the certificate on the client side - is it valid?

Thank you,

Alex.

It is the TS on SMP, I've tried repairing by running the TaskServerSetup_x64.exe, I'm not sure what ARP means.

So it looks like the certificate had something to do with it; I exported it from the server and installed it on a workstation and am now seeing more task logs, but it still doesn't seem to be registering to the Task Server. Here are some of the logs I'm seeing:

<event date="09/23/2015 11:50:56.4680000 -04:00" severity="8" hostName="COMP7" source="Client Task Agent" module="client task agent.dll" process="AeXNSAgent.exe" pid="6860" thread="7136" tickCount="681724649"><![CDATA[CTaskAgentBase::ProcessTasksThreadProc(): Registration is in progress, check for tasks is postponed.]]></event>

It flipped between these two states a couple times:

<event date="09/23/2015 11:50:56.4710000 -04:00" severity="8" hostName="COMP7" source="Client Task Agent" module="client task agent.dll" process="AeXNSAgent.exe" pid="6860" thread="7136" tickCount="681724665"><![CDATA[CTaskAgentBase::_SetAgentState(): Change of state [CTA_STATE_CheckingForTasks] to state [CTA_STATE_NotRegistered] is allowed.]]></event>

Then these failures as far as registering:

<event date="09/23/2015 11:50:56.4710000 -04:00" severity="8" hostName="COMP7" source="Client Task Agent" module="client task agent.dll" process="AeXNSAgent.exe" pid="6860" thread="7136" tickCount="681724665"><![CDATA[CTaskAgentBase::_IsRegistered(): result [not registered].]]></event>

<event date="09/23/2015 12:36:32.6180000 -04:00" severity="2" hostName="COMP7" source="Client Task Agent" module="client task agent.dll" process="AeXNSAgent.exe" pid="6860" thread="9712" tickCount="684460689"><![CDATA[Failed to call web interface by url [http://AltirisServer.Domain.com:80/Altiris/ClientTaskServer/Register.aspx?lastResort=true&resourceGuid=0b29e1b5-db66-4d1f-a7e0-6c3df676860c&crc=00070006001A064F], error [0x80042D21, IDispatch error #11041].]]></event>

<event date="09/23/2015 12:36:32.6200000 -04:00" severity="8" hostName="COMP7" source="Client Task Agent" module="client task agent.dll" process="AeXNSAgent.exe" pid="6860" thread="9712" tickCount="684460689"><![CDATA[RegisterWithTaskServerOp::_register(): Completed with [FAILED (may retry)].]]></event>

Also here's a view of the Task Service; it shows the computers as being registered as of 09/15 but this isn't reflected in any of the agents on the clients or in RAAD:

Have you tried to open this NS URL https://AltirisServer.Domain.com:443/Altiris/ClientTaskServer/Register.aspx on your client PC, where this problem occurs?

Does it show this in I.E on client? Or it doesn't open it?

Called without 'resourceGuid' parameter or with invalid

Just to clarify:

You always had this problem or this problem has appeared unexpectedly?

As far as I see on screenshot, you have different versions of Client Task Agents so you had an upgrade maintenance - Make sure that Task Server and Symantec Management Agent are up-to-date.

Thanks,

IP.

Please take a look at report: "Reports -> Notification Server Management -> Registration -> Agent Registration Status" - might it be that some agent are in "blocked\pending\revoked" state?

Also, might it be that task server on NS has some low limit for the number of clients it could handle? Please check policy: Settings -> Notification Server -> Site Server Settings -> Task Service -> Settings -> Task Service Settings

If possible, please collect and attach logs with debug information on a client that has issues with registration:

1. Run SMA-debug-logging.reg on a client

2. Delete all files from "\ProgramData\Symantec\Symantec Agent\Logs"

3. Restart SMA agent service ("Symantec Management Agent"), wait for 2-3 minutes

4. zip and attach "\ProgramData\Symantec\Symantec Agent\Logs" folder

It will be really good if you may also turn-on max log level on SMP and attach NS logs while agent will try to register, but as NS logs might be quite big, we may start with agent logs only.

Thank you,

Alex.

Attachment(s)

SMA-debug-logging.zip   343 B 1 version

This is the message I get when trying to reach that URL from a computer with the updated Task Agent:

<response result="failure" code="7" description="The handler 'Register' is failed to process request. Called without 'resourceGuid' parameter or with invalid.">The handler 'Register' is failed to process request. Called without 'resourceGuid' parameter or with invalid.</response>

Hello, I'm seeing the same behavior in my environment.  I have two test clients for which I have repeatedly uninstalled and reinstalled the agent.  When any patches attempt to install, the pre-download detection check fails with error 2 which indicates that the patches are not detected and need to be installed.  However, the pre-download detection check never changes to compliant or not-compliant.  The status of the pre-download detection check remains at "in progress".  Therefore, no patches ever install.  I get the same message when accessing the NS using URL https://AltirisServer.Domain.com:443/Altiris/ClientTaskServer/Register.aspx.

<response result="failure" code="7" description="The handler 'Register' is failed to process request. Called without 'resourceGuid' parameter or with invalid.">The handler 'Register' is failed to process request. Called without 'resourceGuid' parameter or with invalid.</response>

I would appreciate any assistance.  Thanks.

Hi Alex,

Attached is are the zipped log files. I noticed another message showing up saying "Server ID {...} is invalid" not sure if that's related to this at all. I'm not sure how to enable max loging on SMP, but if you can provide steps I'd be more than happy to try checking the logs from there as well.

Thanks

Attachment(s)

Logs_50.zip   92 KB 1 version

Hello mconyers, have you found anything new about this error since Monday?

I've created a case with support so if they can help me figure out what's going on I'll update this forum with any helpful info.

Hi,

May you try to run command on a task server and see if it will help clients to register?

aspnet_regiis.exe /iru

 The Aspnet_regiis.exe file can be found in one of the following locations:

%windir%\Microsoft.NET\Framework\v4.0.30319

%windir%\Microsoft.NET\Framework64\v4.0.30319 (on a 64-bit computer)

(note: for Win81\2012 OS run "dism /online /enable-feature /featurename:IIS-ASPNET45")

Thank you,

Alex.

Thanks Alex, but this did not cange anything. I did install the agent on another server in the attempt to make this one a stand-alone Task Server, however, the agent won't even get through the initial registration of the agent, nevermind the Task Server registration. I've attached the inital log file that was produced from the server that can't register. I'm still waiting to hear back from support so if you have any other suggestions I'm willing to try anything at this point.

Attachment(s)

Agent1_0.txt   101 KB 1 version

After logging a ticket with support we found this was due to a file becoming corrupt after attempting a repair on the Management Suite. We needed to uninstall Task Server manually using the executable in C:\Program Files\Altiris\Notification Server\NSCap\bin\Win64\X64\Client Task Management\Server Package, then perform another repair, and reinstall the Task Server using the same executable. The best way to check to see if this is working is to run netstat -an and make sure ports 50121, 50123, and 50124 are listening. These are the ports associated with Task Server.