KNOWN ISSUE: Unable to Import a Detailed Export of a Software Resource

Products

• Software Management Solution

Issue/Introduction

Unable to Import a Detailed Export of a Software Resource, error thrown:

Log File Name: C:\Program Files\Altiris\Notification Server\Logs\a.log
Priority: 1
Date: 4/22/2010 1:48:56 PM
Tick Count: 10830703
Host Name: NS7PARIS
Process: w3wp (4012)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.NS.UI.MenuItemsCommon.ImportItem
Description: An error occuring during 'ImportItem': Altiris.NS.Exceptions.AeXItemImportException: Invalid item XML format.
   at Altiris.NS.ItemManagement.LegacyItemConversion.ConvertNS5Item(XmlNode itemNode)
   at Altiris.NS.ItemManagement.Item.ImportItem(XmlNode itemNode)
   at Altiris.NS.ItemManagement.Item.ImportItem(String itemXml)
   at Altiris.NS.UI.ConsoleMenuItems.ImportItem(Guid parentGuid, String xml)

Selecting different options during the Detailed Export doesn't make a difference in the import results.
Also attempts using the ImportExportUtil.exe application fail with the same error as well.

Resolution

As of Symantec Management Platform 7.0 SP3 MR4 and also the version 7.1, the use of the CS script is no longer necessary to import  a detailed export - you simply right click on the Software Catalog folder in the tree view and then choose Import. Please note that this can't be done choosing the Manage\Software Catalog menu option with the Activity Center installed.

If the Activity Center is installed you will need to go to the following location to perform the import:
1. Click Settings->Console->Views
2. Expand Software
3. Right click on Software Catalog & choose import.

***

Should you be unable to update to MR4 or 7.1, you can use the following workaround instead:

• Copy the script and the exported XML to the \Program Files\Altiris\Notification Server\Bin
• Type nscript.exe importsoftwareresource.cs <name of your exported XML file>
  Example: nscript.exe importsoftwareresource.cs SEP12.XML

Please note that this script is provided as is and that the Symantec recommended solution is the upgrade to MR4.

Applies To

This has been seen on SMP 7 SP3 / SMS 7 SP1 and SMP7 SP4 /SMS 7 SP2 environments.

It is resolved in SMP 7 SP3 MR4 and SMP 7.1.