A Data Connector import rule fails and errors occur when viewing the import rule log.

ITMS 8.x

Various.

The following are some of the many possible error messages that can appear in an import rule log. Others can be found by searching the Symantec Knowledge Base for the specific error. As such, this is not an all-inclusive list. Most error descriptions are clearly defined as to why they fail, which is usually because of a logical issue from the data value or attempt to use the data in an incorrect manner. Also, some "errors" are merely warnings and can be safely ignored, as the message may simply indicating that the row was skipped because no data was present, which may be what the user intended.

Note: An error usually will mention that something is being skipped. Usually this does not indicate that the entire row will be skipped. But this depends on the context of the error. Be sure to evaluate what is in red (the problem data classes) in conjunction with what the error is stating. For example:

"Row x skipped for data class '<data_class>'. Multiple rows of data for the same resource are redundant for single-rowed data classes."

This would seem to imply that the entire row will be skipped. This is actually incorrect, in that this is only ignoring the incorrect attempts to assign multi rowed data classes to a single-rowed data class. The row is kept and updated with the remaining data classes that are not part of this. For example: If the serial number for a computer was included in two lines for the computer, where cost items are being imported, this error will occur. The first record will create the resource and add the serial number and first cost item. The second record will update the computer, skip setting the serial number (and throw the error in the log), and continue updating the remaining data classes as applicable.
 

• Error: Entire row <row number> skipped. Importing this row would create a new resource in the NS and resource creation has been disabled for this import rule.
  Solutions: (1) The resource doesn't exist and therefore cannot be appended or updated by the import rule. Turn on resource creation by enabling "Create resources if doesn't exist". (2) for Symantec Management Platform 7.5 without any hot fix, this is a known defect. Apply the latest HF to resolve this. Further information about this can be found here:
  
  Using any lookup key except Resource Name in a Data Connector import rule creates duplicate records or skips updating existig records
  http://www.symantec.com/business/support/index?page=content&id=TECH213120
   
• Error: Row <row number> skipped for association <association name>. Lookup using resource key <resource key name> did not find a resource.
  Solution: An attempt to create an association to the resource was made, but the associated resource does not exist in the database. For example, if a location association is being attempted to a computer, "Springfield", this must first exist in Home > Service and Asset Management > Manage Configuration Items > Organizational Types > Location. The association must be spelled exactly the same as it appears in the data, as well. Likewise, a resource import will not also create the associated resource. For example, importing computers will not also import new locations. Any association or foreign key must already exist before being attempted to be associated. Further information about this can be found here:
  
  Data Connector import rule fails to import associations such as Asset Owners, Cost Centers, Departments or Locations
  http://www.symantec.com/business/support/index?page=content&id=TECH215869
   
• Error: Row <row number> skipped for data class 'Cost Items'. Unable to convert value to data type required for destination column 'Amount'. Value '$100.00' could not be converted to required data type float or real. Input string was not in a correct format.
  Solution: Do not include the dollar symbol "$" for field values that are monetary. For example, "$100" will fail, whereas "100" will not.
   
• Error: Row <row number> skipped for association 'Location'. Maximum cardinality for association type reached.
  Solution: More than one record included a Location for the same resource. If the association is one to one, which most are, then additional attempts, accidental or otherwise, will result in this error. Only set a resource's Location in the first record to be imported for it, not in any subsequent records. This can happen when multi rowed records are also imported, such as cost items, and unique values may then be accidentally attempted to be imported in per each record.
   
• Error: Row <row number> skipped for data class <data_class>. Multiple rows of data for the same resource are redundant for single-rowed data classes.
  Solution: This can  happen if multi rowed records (one to many data classes, such as cost items) are imported for the same resource. When this occurs, either the resource lookup key was referenced more than once, such as a computer or user name, or a unique key data class was, such as a serial number. This is generally safe to ignore, as the normal reason is to bring in multi rowed data classes, where the resource lookup key is expected to be present on more than one row of data. Additional information about this can be found in the following article:
  
  Error "Row x skipped for data class '<data_class>'. Multiple rows of data for the same resource are redundant for single-rowed data classes." occurs when using a Data Connector Import Rule with duplicate key field values
  http://www.symantec.com/business/support/index?page=content&id=TECH202602
   
• Error: Row <row number> skipped for data class 'Cost Items'. Multiple rows of data for the same resource is not allowed while using Update mode on a data class without key columns.
  Solution: For multi rowed records, the Update Mode usually will need to be changed from Update to Append, to enable multiple updates to occur correctly. Additional information about this can be found in the following articles:
  
  Data Connector Import Rule fails to set a foreign key correctly
  http://www.symantec.com/business/support/index?page=content&id=TECH192860
  
  How to use Data Connector to import multi rowed data classes
  http://www.symantec.com/business/support/index?page=content&id=HOWTO95371
   
• Error: Row <row number> skipped for data class "Purchase Order Information". Multiple rows of data for the same resource are redundant for single-rowed data class.
  Solution: This is not a real error and can be safely ignored, as it is only alerting the user that multiple line items were imported in using the Append mode. Additional information about this can be found in the following article:
  
  Data Connector Import Rule fails to set a foreign key correctly
  http://www.symantec.com/business/support/index?page=content&id=TECH192860
   
• Error: Row <row number> skipped. Null values found in one or more resource key lookup columns.
  Solution: A column's required value was null (empty). The user must specify a value for this column in the data. For example, if the User resource type was used with the resource lookup keys of UserID/Domain, neither UserID or Domain can be blank. If one or both are, the entire row is skipped.
   
• Error: Row <row number> skipped association 'Location'. Null values found in one or more key lookup columns.
  Solution: No Location value was provided in the data. This may have been intended by the user and therefore not a real error and may be able to be safely ignored.
   
• Error: Row <row number> skipped for data class 'Cost Items'. Data class foreign key lookup on column 'Type' failed.
  Solution: No Type value was provided in the data. This may have been intended by the user and therefore not a real error and can be safely ignored.
   
• Error: Row <row number> skipped for data class 'Ownership Details'. No value has been specified for non nullable destination column 'Ownership Percentage' and there is no existing value for this column in the NS database for this resource.
  Solution: Add a value greater than blank/null to the Ownership Percentage.
   
• Error: Row <row number> skipped for data class 'System Number'. All columns contain null values.
  Solution: A value must be specified for any column and cannot be blank when updating existing records. Additional information about this can be found in the following articles:
  
  Data Connector Import Rule fails to remove a specific column's existing value
  http://www.symantec.com/business/support/index?page=content&id=TECH202549
   
• Error: String value in row <row number> of data class <data class> column <column name> has been truncated to fit destination column.
  Solution: The alphanumeric (string) value provided in the data exceeds in length the data class' length. This can occur for any data class type but most commonly for string types. For example, if a data class is only nvarchar(10), this allows only up to ten alphanumeric characters. Anything more than that is truncated after the 11th+ character. If this is a custom data class, the user should delete it and recreate it, to accommodate the maximum largest value that is expected.
   
• Error: "(X) The import rule '<rule name>' failed. Error: There is no row at position <row number>." This error will actually occur when the import rule is running, which will abort the run. The cause is unknown, but in one instance, was tracked down to a corrupted computer record, the one referred to by <row number>. Deleting this computer in the CMDB resolved the issue (and therefore, the rule wasn't able to try to update the specific record).

Related Articles

How to troubleshoot import issues when using a Data Connector import rule
http://www.symantec.com/business/support/index?page=content&id=TECH195835

How to import data using a Data Connector Import Rule
http://www.symantec.com/business/support/index?page=content&id=HOWTO79380