KNOWN ISSUE: Connector failing to import resources with the same name but different types

Article:TECH12819

Created: 2006-03-07

Updated: 2009-10-27

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

NOTE: If you are experiencing this particular known issue, we recommend that you 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

Languages

Show all

Problem

When importing data using Connector, it checks across resource types for uniqueness when using resource name as the resource lookup key.

Environment

Notification Server 6.0 SP3 (6.0.6074)
Connector Solution 6.1

Cause

When importing data using Connector, it fails to create "Altiris" root node and cannot correctly build hierarchy tree.

This fix rolls back the original SP3 change. So while this fix will fix Connector Solution on 6.0 SP3, the problems with code introduced by SP3 will not be addressed until Notification Server 7.0.

Solution

This issue is resolved within Notification Server 6.0 SP3 Rollup Pack 6. This Rollup Pack has been superseded and all fixes are included within the latest Rollup Pack.

Symantec recommends installing the latest rollup pack via the Solution Center found at Configuration > Upgrade/Install Additional Solutions.

Release notes can be found at article 34317.

Supplemental Materials

Source	DEFECT
Value	SYD 25681
Description	Logged in sydd2 (Altiris - Sydney) database

Legacy ID

20435