Video Screencast Help

Inv_AeX_SWD_Execution_Summary table is not getting updated.

Created: 25 Jan 2013 • Updated: 14 Feb 2013 | 3 comments
shrishail.jivani's picture
This issue has been solved. See solution.
In SMP 7.1 SP2 MP1 the table “Inv_AeX_SWD_Execution_Summary” is not getting updated in our Altiris Database. This table is required to track the status of Software delivery and Patch management. Inventory is running up to date (Full inventory/Hardware/software) and getting updated Add remove table and other tables too. I checked log files and found that there is an issue with Task servers, The TS was older version and have upgrdaed to newer version,but still this table is not getting updated. Any idea?

Comments 3 CommentsJump to latest comment

andykn101's picture

I think this is populated by an overnight task that uses data from other tables, like the Inv_Hardware_Summary explained here:

So the NS.Nightly task will probably trigger a Stored Procedure.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

jasonfo's picture

I ran into something similar before. Try this...

If that does not work then check to make sure that table is being logged. Check settings, notification server, resource data class and association history, software delivery summary. Enable those 3 and see if that does it.

Check Settings, Agents/plug-ins, Symantec Management Agent, Settings, Symantec Management Agent Settings - Global. on the Events tab make sure all the boxes are checked that you want to report on.

Finally, go to settings, notification server, purging maintenance. On the Resource Event Data Purge Settings tab increase the max table rows to 1 million.

shrishail.jivani's picture

Thanks , workaround it's working now, but i got some info from symantec as described below. "We are aware of an issue where the SMA fails to send program execution event messages, and it is due to a synchronization problem while monitoring and sending NSE files on the agent side. We have already addressed this in our 7.5 code and are currently looking at back porting the fix to 7.1.2 in our planned MP1 v4RU package which will be released during either March/April this year. I suggest you open a case with support so that they can associate it with the relevant eTrack in order for you to be notified when v4RU i available"