Monitor Solution is Generating Format Exception Error in Logs

book

Article ID: 159085

calendar_today

Updated On:

Products

Monitor Solution Monitor Pack for Servers Monitor Solution for Servers

Issue/Introduction

Monitor Solution is generating a Format Exception error in the server logs. It does not appear to be causing any performance issues, but the error does occur regularly. 

<event date="02/28/2014 21:21:46.4099771 +00:00" severity="1" hostName="SMP-W2K8-01" source="Altiris.Monitor.Common.ATrace.ReportInternal" module="AeXSVC.exe" process="AeXSvc" pid="1500" thread="55" tickCount="1692317176"><![CDATA[Thread:0055 PerfBlobHandler.OnMessage:  FormatException('Input string was not in a correct format.')
System.FormatException (mscorlib): Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at Altiris.Monitor.Solution.PerfBlobHandler.HandleEventNodes(MetricsWriter writer, Guid machineGuid, XmlNodeList xmlNodeList)

Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)
   at Altiris.NS.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.Monitor.Common.ATrace.ReportInternal(Category category, String message, Exception ex, Int32 stackLevel)
   at Altiris.Monitor.Solution.PerfBlobHandler.HandleEventNodes(MetricsWriter writer, Guid machineGuid, XmlNodeList xmlNodeList)
   at Altiris.Monitor.Solution.PerfBlobHandler.OnMessage(String message, MetricsWriter writer)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.DispatchWithinContext(String message, Boolean useFilename, IItem item, IItemMessaging iim, MessageHeader header)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.DispatchWithinContext(String message, Boolean useFilename, Int64 eventId, MessageHeader header)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.Dispatch(String message, Boolean useFilename, Int64 eventId, MessageHeader& header)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.PerformDispatch(DispatchSlot slot)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.DispatchSingleNse(DispatchSlot slot)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.WorkerDispatchStep(DispatchSlot slot, IAutoCallContextSnapshot snap)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.WaitAndDispatch(ThreadDatabaseContext`1 ctx, WaitHandle[] waiters, DispatchSlot slot, IAutoCallContextSnapshot snap)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.WorkerLoop(Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)

**CEDUrlStart** :http://entced.symantec.com/entt?product=SMP&version=7.5.1670.0&language=en&module=bPdpENkDirkzvsLj2PcvdE3aP4yzdaiEMEDwqu9CVpmXtkzvDW6NPLu3Lfg+sPKR&error=-1545231900&build=**CEDUrlEnd**
]]></event>

Cause

This issue can be reproduced when a user creates an NT event rule and am alert based on that rule is triggered. The monitor agent will create one extra <ntevent> XML tag in the MetricLog.xml file but the tag is empty. On the server side, when MetricLog.xml is parsed, it cannot parse that <ntevent> tag and does not store it in the database.

Resolution

The Monitor Solution development team has confirmed this issue is fixed in ITMS 7.5 SP1 which will be released in the first part of June 2014. Please subscribe to this KB for future updates.


Applies To

Monitor Solution 7.5
ITMS 7.5