KNOWN ISSUE: Item has already been added. Key in dictionary: "HPCMS WMI HP BIOSSensor".

Article:TECH41446  |  Created: 2009-02-18  |  Updated: 2009-09-15  |  Article URL http://www.symantec.com/docs/TECH41446
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



The following error occurs when trying to populate the Default Column Mappings for an AD Import Rule (in this case Computers AD Import Rule):

Priority='1'
Date='Feb 16 10:22:57'
Tick Count='424917375'
Host Name='NSServer'
Process='w3wp.exe' (2816)
Thread ID='8132'
Module='AltirisNativeHelper.dll'
Source='Altiris.DirectoryServices.UI.ColumnMappingsSelectDlg.LoadPageControls'
Description=System.ArgumentException caught in LoadPageControls. Reason: Item has already been added.  Key in dictionary: "HPCMS WMI HP BIOSSensor"  Key being added: "HPCMS WMI HP BIOSSensor" ( Unhandled exception.  Type=System.ArgumentException Msg=Item has already been added.  Key in dictionary: "HPCMS WMI HP BIOSSensor"  Key being added: "HPCMS WMI HP BIOSSensor" Src=mscorlib
StackTrace=
   at System.Collections.SortedList.Add(Object key, Object value)
   at Altiris.DirectoryServices.UI.ColumnMappingsSelectDlg.LoadPageControls() )


Environment



Notification Server 6.0.6074 SP3
Altiris Integrated Component for Microsoft Active Directory   6.1.842
HP Client Manager 6.2.x

Solution



A workaround has been developed by our development team to rectify this problem.  

To utilize this workaround, first download the attached 'HPConfig.zip' file and unpack the archive.  The archive contains two updated configuration files for the HP Client Manager software.

Notes:  It is highly recommended that a backup of the existing database be taken BEFORE proceeding with the steps below.

Warning: This process deletes the 'Inv_HPCMS_WMI_HP_BIOSSensor' table, so it’s recommended to take the Backup of existing Data Base prior to make these changes. 

 

1.       Run the following queries so you can identify if there are currently two duplicated for HPCMS WMI HP BIOSSensor:

Select *

From Item

Where Name = 'HPCMS WMI HP BIOSSensor'

 

Select *

From DataClass

Where Name = 'HPCMS WMI HP BIOSSensor'

 

2.       You should see two entries with the same name but different GUID.

 

At this point a valid workaround is the following:

-- Run the provided config files for a workaround  as below,

 

a.    First use AeXConfig.exe to configure the ‘BIOSSensor_Inv_HPCM_1.config’ file with the following command:

 “[NS INSTALL DRIVE]:\Program Files\Altiris\Notification Server\bin>AeXConfig.exe /configure [COMPLETE PATH of Config file]\ BIOSSensor_Inv_HPCM_1.config”.

 

b.    Then use AeXConfig.exe to configure the ‘BIOSSensor_Inv_HPCM_2.config’ file with this command:

 “[NS INSTALL DRIVE]:\Program Files\Altiris\Notification Server\bin>AeXConfig.exe /configure [COMPLETE PATH of Config file]\ BIOSSensor_Inv_HPCM_2.config”

 

Summary of changes:  These configuration files are changing the ITEM Table and the DATACLASS Table 'Name' attribute associated with one of the duplicated dataclass names to 'HPCMS WMI HP BIOSSensorInv'.  This will also rename the table associated table with this dataclass.


Attachments

HPConfig.zip (2 kBytes)

Supplemental Materials

SourceDEFECT
ValueSYD 40255
DescriptionLogged in sydd2 (Altiris - Sydney) database

SourceDEFECT
ValueETK 1585687
DescriptionLogged in Etrack (Symantec) database

Legacy ID



45631


Article URL http://www.symantec.com/docs/TECH41446


Terms of use for this information are found in Legal Notices