KNOWN ISSUE: Symantec Management Agent attempts to send all locally queued NSE files when PostEvent.aspx is not available


Article ID: 158404


Updated On:


Management Platform (Formerly known as Notification Server)


When the Symantec Management Agent is unable to send data back to the Symantec Management Platform through the PostEvent.aspx page, the agent will queue the information locally as a NSE file until a later time when communications can be established.  By design the agent initiates a retry interval to send locally queued NSE files back to the server.  The interval begins at 3 minutes, then again at 6 minutes, eventually reaching the maximum retry interval of 60 minutes.  At each interval, the agent will attempt to resend all queued NSE files one by one.  The longer the agent remains offline to the server the more items can potentially be queued locally causing additional connection attempts to the SMP server.


Log entries may vary depending on why PostEvent.aspx is not available, but in general there will be a repeating pattern corresponding to the agent retry interval with a failed postevent message for each of the locally queued NSE files.  One such example may be:

PostFile to 'http://SMP-SERVER/Altiris/NS/Agent/PostEvent.aspx?priority=0&source=EB32DCE2-E225-4AB9-8758-05159732E36B' failed: HTTP Request Failed: The operation completed successfully.



While PostEvent.aspx is unavailable, the agent is not handling the responses correctly and therefore attempts to send each locally queued NSE file in sequence.



A pointfix is available for the ITMS 7.1 SP2 MP1.1 platform, which is available through Symantec support upon request.  With the pointfix applied, when the retry interval begins and the agent fails to send the first queued NSE file, the response will be correctly handled the first time preventing additional retries for each file in the queue.

Development is working to provide this fix in an upcoming rollup hotfix.


Applies To

Symantec Management Platform 7.1 SP2