Discovery and Inventory Group

Component or Association missing

A common issue after an install or upgrade appears when agents are not installing or upgrading their Inventory Plugins. This happens due to a condition where a configuration item gets dropped during the install / upgrade process. This might be the entire package configuration, or an association to it. In the logs the following error or one similar will appear when clients request their configuration:

"2/25/2011 11:01:16 AM","Unable to generate policy XML for item: 8592325b-1b4a-4cf4-8c46c17a0ba564a2

**CEDUrlStart** :http://entced.symantec.com/entt?product=SMP&version=7.1.6797.0&language=en&modul e=qlub65YMYgWeGGssRthgvN1WHJjANnIAgZtUStOHQto=&error=862971658&build=**CEDUrlEnd**  

( Exception Details: Altiris.NS.Exceptions.AeXException: Unable to build the client configuration XML for advertisement with guid {8592325b-1b4a-4cf4-8c46-c17a0ba564a2}. Reason: Did not get a row for Software Delivery Advertisement ""Inventory Plug-in - Install"", Guid = {8592325b-1b4a-4cf48c46-c17a0ba564a2} from the SWD tables. ---> Altiris.NS.Exceptions.AeXException: Did not get a row for Software Delivery Advertisement ""Inventory Plug-in - Install"", Guid = {8592325b-1b4a-

4cf4-8c46-c17a0ba564a2} from the SWD tables.   at Altiris.NS.StandardItems.SoftwareDelivery.AdvertisementItem.OnBuildClientConfigXml2(Guid workstationGuid, XmlNode requestDocumentElement, XmlTextWriter xmlBuilder)

  --- End of inner exception stack trace --- 

 

There are 3 ways to resolve this issue. Each subsequent method involves more work, so it is recommended to go through the easiest first, and only proceed if it does not work.

 

First Method

This method requires a working environment. Support can supply a working package to complete these steps.

1. In the Symantec Management Console browse under Manage > All Resources.
2. Browse in the right-hand pane under Default > All Resources > Package > Software Package.
3. In the search field in the right-pane, found in the upper right, type: Inventory
4. Find the Inventory Plug-in for Windows Package, right-click, and choose Export.
   
5. Save the file, and transport it to the Notification Server that is having the issue.
6. At the same location above, right-click on Software Package and select Import.
7. Browse to the file that was copied over in step 5.
8. Done! In many cases this resolves the issue.

 

Second Method

The second method does not require a working environment, but requires additional steps. It is recommended to take a backup for your database before using the second or third methods to resolve this issue. This is only a precaution, and I have not had issues with these methods in the past.

1. In the Symantec Management Console, browse under Manage > Software.
2. In the left-hand pane browse under All Software and select All Software Releases.
3. In the search field located at the top, type Inventory Plug-in
4. In this list, locate all versions for the Inventory Plug-in for Windows.
5. For any entry that shows a disk for the icon (seen in the screenshot for step 10) right-click and choose Delete.
6. Right-click on the resource that contain packages, shown as a different icon, and choose Properties.
7. Copy out the Guid listed for this resource.
   
8. Run the following query against the database, using the GUID found from step 7.

UPDATE RM_ResourceSoftware_Release

SET Attributes = '0'

WHERE [Guid] = '80328534-9d5c-4343-bcad-bda7ecf9621f'

9. Reload the Symantec Management Console and browse back to Software, using the search filter.
10. Right-click on the Software Resource for the Inventory Plug-in for Windows and choose Delete.
    
11. Make sure no Inventory (disk) or Release (computer with disk) plug-in items remain.
12. Open a command window (right-click, Run ad Administrator).
13. Browse to the following location where the platform is installed: 

\Program Files\Notification Server\Bin\

14. Now run the following command-line, NOTE that locations will need to be set to your install directories:

C:\Program Files\Notification Server\Bin\AeXConfig.exe /configure

“C:\Program Files\Altiris\Inventory\Config\Inventory.config”

15. To review the progress, open Log View and filter on “AeXConfig”. This will allow you to see the entries as the reconfigure is occurring.
16. Done! If this does not resolve the issue, the logs gathered during the reconfiguration are vital.

 

Third Method

The third method uses a more messy, dramatic approach. It also requires the steps used in the previous approach.

1. Walk through steps 1 through 11 of the Second method.
2. From the logs gathered during steps 12 through 16 of the second method, you’ll find an import error. This will include reference to the GUID found in step 8 of the second method. The key to this error is finding the other GUID in the error that causes the import to fail. Once that GUID is found, proceed.  Message will state: “Unable to import resource (ref), a duplicate resource (ref) already exists”
3. Open the following URL, which is a search query to use: www.symantec.com/docs/HowTo1191

Paste the query into SQL Enterprise Manager. Change the GUID to the one found in the message to the location marked /* Enter Search Guid here */

/*

    Last Revision: 3 August 2012

*/ 

set transaction isolation level read uncommitted

 

/* Declare variables */ declare @strSql nvarchar(max),

    @searchguid uniqueidentifier,

    @lowrow smallint,

    @SrchEvtTables bit,

    @SrchCharTypes bit,

    @SrchTextTypes bit,

    @CharTypeColName varchar(200) 

 

/* Enter Search Guid here */

set  @searchguid = ltrim(rtrim('3e71856b-aadb-48d8-8264-0b36d1aac224')) 

/* Search Event Tables: If you wish to disable searching the event tables then set 

   @SrchEvtTables to 0.  This option was added since the event tables can get quite large 

   and many of the guid columns in them are not indexed. Disabling this will speed up the     query in such cases (at the cost of not searching those tables). 

   (Enabled: 1, Disabled: 0) */ set @SrchEvtTables = 1

 

/* Search Character Type Columns: There are some columns in the database that hold GUIDs, 

   but the column is not a uniqueidentifier type (they have the GUID as a character string

   instead).  If you want to search character column types (char, nchar, varchar, and nvarchar) then you must set the @SrchCharTypes value to 1.  

1. The results may take a minute or longer to complete. The last column contains Select statements.

Select the entire column by clicking on the column header, and copy the data.

2. Paste the data into a new query window.
3. Hit Ctrl + H to bring up the find and replace window.
4. Search for: SELECT *
5. Replace with: DELETE
6. Once done, run the query to delete this object from the database’s tables.
7. Now run through steps 12 through 15 of the second method.
8. Done!

 

If the problem persists, please contact Symantec Support for assistance.