Client Management Suite

Error:  BaseXMLHttpCallback Exception:  An exception occurred while excuting the request

System.Exception:  System.Xml.XmlException:  Unable to find node named "statusEvt".  Found node " " instead at Altiris.DotNetLib.Xml.XmlTextReaderHelper.MoveToExpectedNode (XmlReader r, String nodeName)......

BaseXmlHttpCallback Exception: System.Exception: An exception occurred while executing the request ---> System.Exception: System.Xml.XmlException: Unable to find node named "statusEvt".  Found node "" instead

Found the following article which is related to 7.0 and we are on 7.1 sp2

http://www.symantec.com/business/support/index?page=content&id=TECH136471

Curious if there is a solution to this issue now in the 7.1 SP 2 environment.  Seems to happen after and informational update related to:

RemoteClientTaskManager:: ClientConnectivityThreadStart():  Registered 1 client records

Correct.  You can ignore it.  Unless there's more to the error I don't see anything bad here.

http://www.symantec.com/docs/TECH175078

"Until the issue is resolved in SP2, the issue can be manually resolved in the following manner:
The error will reference a machine name (by GUID, if using LogViewer on the NS it will resolve the name). Typically only 1 or a handful of machines will be in this state.
Access the system(s) in the errors and delete the Status events, located at: C:\Program Files\Altiris\Altiris Agent\TaskManagement\status\.
Once these files are deleted, the Agent stops the looping requeuing logic.

You can use a Script to delete the contents of the folder, that can be pushed down as a Task, for example:

@ECHO OFF

IF EXIST "C:\Program Files (x86)\Altiris\Altiris Agent\TaskManagement\status" (
CD "C:\Program Files (x86)\Altiris\Altiris Agent\TaskManagement\status"
DEL *.XML /Q
)

Hi

I've figured out the same issue in our 7.1 SP2. Since last week, this error ocours every 10 seconds.
Also the DB grows up from 4 to 8 GB since the last week.

This articel didn't help me because no TASK GUID is displayed.

http://www.symantec.com/docs/TECH175078

I think I will contact the support to have a look to this issue.

"05.06.2012 09:17:18","BaseXmlHttpCallback Exception: System.Exception: An exception occurred while executing the request ---> System.Exception: System.Xml.XmlException: Unable to find node named ""statusEvt"".  Found node """" instead
   at Altiris.DotNetLib.Xml.XmlTextReaderHelper.MoveToExpectedNode(XmlReader r, String nodeName)
   at Altiris.TaskManagement.Common.ClientTask.Events.AltirisServerClientTaskRunEvent.OnFromClientXml(XmlTextReader r, String nodeName, AltirisResourceGuid resourceGuid)
   at Altiris.TaskManagement.Common.ClientTask.Events.AltirisServerClientTaskRunEvent.FromClientXml(XmlTextReader r, String nodeName, AltirisResourceGuid resourceGuid)
   at Altiris.ClientTask.Server.ClientTaskServer.ProcessPostClientStatusXml(AltirisResourceGuid resourceGuid, String statusType, XmlTextReader r)
   at Altiris.ClientTask.Server.ClientTaskServer.ProcessPostClientStatusXml(String statusXml)
   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.ProcessPostClientStatus(XmlTextWriter wr, NameValueCollection queryValues, Stream requestStream, Int32 contentLength)
   at Altiris.ClientTask.Server.HttpHandlers.PostStatus.WriteResponse(XmlTextWriter wr)
   at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)
   at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)","Altiris.TaskManagement.ClientTask.*","w3wp","96"
 

Just run the batch script that andykn101 posted on all your devices.

I've rolled out this script to all of our managed systems.

But the problem still exist.

Then you may have to go down this path.

https://www-secure.symantec.com/connect/articles/cwoc-2010-aila-050-samples-using-query-shell-part-ii