General Troubleshooting and Suggestions

The following suggestions are ways to troubleshoot issues using a Data Connector Import Rule. Additional troubleshooting and setup and configuration information can also be found in the following article:

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

• When creating a new Import Rule, start simple. Do not try to add in very many data classes at first, and then use the Test button to check if what will be brought in will work. Then, add additional data classes, and finally, add in any associations or reverse associations. Use the Test button to check these periodically while adding them. The reason for doing this is if many data classes and associations are added all at once without verifying them by using the Test button, it then becomes much more complicated to troubleshoot to tell what went wrong, where.
• Likewise in testing, use a small number of records that are a sample and represent what will be later imported in. The same reasoning applies here as the previous suggestion. The simpler the scenario variables and environment, the easier it is to troubleshoot any issues and find and resolve the root cause. Later, after the Import Rule has been successfully tested, then the full data set can be used.
• Once everything is set, again use the Test button. If any errors occur, verify if these are expected as outlined in the Error Messages section, or if they require troubleshooting. If the latter, do so, then once everything is set, use the "Run now" button.
• For additional precautions, use the "Run now" button to commit the data to a test server before doing so on the production server. It may be very difficult if not impossible to remove records or changes once they are committed to the database by the "Run now" button; use caution when using Data Connector because of this potential risk to the database.
• When using the "Select data classes" link, custom data classes will not by appear for selection if they have not been assigned to the resource type.
• When using multi rowed records, such as cost items, do not duplicate unique one to one field values, such as attempting to set a serial number or location more than once. Trying to do so will result in the row skipped and an error. This is described in more detail in the Error Messages section.
• In rare situations, the specific Import Rule may be corrupted. If everything seems like it should be working but isn't, create a brand new Import Rule, set it up the same way, and then try this version. If this works, simply delete the original corrupted one and use the new one instead.
• Depending on how the Import Rule is set up, the data classes and associations used, the data source (database, .csv file, .xls file, etc.) and version of Data Connector, errors may occur before the Import Rule log is able to be seen. For example, opening or trying to run or test a rule may throw an error. In general, these are not covered in this article, but their cause may be the same as the errors causes listed below. Review these for similar errors and try the listed solutions.
• If an Excel file is used as the data (.xls, .xlsx), its formatting, especially equations if the frames, may cause unusual issues. The easiest way to test this is to copy the same data to a .csv, and test this. If this works, the original Excel file formatting is the issue. Remove or change the formatting to resolve the issue.
• If data columns were changed (renamed, added or removed) from the data file or database, the Import Rule may no longer work correctly and immediately result in an error because it is still coded to attempt to access these when it opens or runs. For example, "This run failed with an error: Failed to get resource <GUID>." To resolve this, point the import rule to use a different data source (or create a duplicate of the import rule), then back to the original data source. This will unfortunately have the side effect of possibly requiring the user to set up the data classes and associations it uses, however.
• If a "missing" or "cannot find" GUID error appears when the Import Rule is opened, especially if this has been imported from another Altiris server, this is usually an indication that a custom data class, resource or association has been deleted or does not exist. Saving the Import Rule should resolve this (but without its prior set up for the missing type).
   

Using the Import Rule Log to Toubleshoot Issues

• The run log (a pop-up window) may display such errors as "<number> rows were omitted data data class '<data class>', etc. These are not the full errors. To see why these lines apparently failed, click on the View log link.
• Reviewing the full log is vital to troubleshooting issues. This log is not to be confused with the Altiris server "a" logs or a Profile trace, which are different and generally won't include the same information and details as the Import Rule log. To view an Import Rule log:
  
  1. View the log:
  
  For new test or run of an Import Rule, in the Connector Rule Run Status window, click on the "View log" link.
  
  For a prior test or run of an Import Rule, in the Import Rule's "Run history" section, select the completed task's "View log" link.
  
  2. In the Rows Processed Details section, note the "Log message" column details for any errors. These will correspond to the errors listed below (which is not all-inclusive).
  3. Compare the errors seen in the log to those listed below in the Specific Error Messages section. Troubleshoot these then as indicated.
  4. Further troubleshooting can be performed by comparing working lines and columns to those that fail. What is the difference in the data? This is often key to understanding why a specific line failed. To further simply this, it is recommended to make a small subset of the data being used, for example, 10 lines or less, some with working lines, some without. This helps to reduce the amount of troubleshooting necessary to begin to understand what went wrong, where.

Specific Error Messages

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. Tips: 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.
 

• Error: Row <line 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 <line number> skipped for association 'Location'. Lookup using resource key 'Resource Name' did not find a resource.
  Solution: The specified Location does not exist as a Configuration Item (Manage > Assets > Organizational Types > Location). Create the Location with the appropriate name then the Import Rule will be able to use this to make the association to. Additional information about this can be found in the following article:
  
  Data Connector Import Rule fails to create association mappings
  http://www.symantec.com/business/support/index?page=content&id=TECH191367
   
• Error: Row <line 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 <line number> skipped for data class 'Serial Number'. Multiple rows of data for the same resource are redundant for single-rowed data classes.
  Solution: This can also happen if multi rowed records are imported for the same resource, similar to the above error. In this case, the first computer record included the serial number, the second did not. This may have been intended by the user and therefore not a real error and can be safely ignored. 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 <line 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 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 <line 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 <line number> skipped. Null values found in oneor more resource key lookup columns.
  Solution: A column's required value was null (blank, empty). The user must specify a value for this column in the data.
   
• Error: Row <line 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 <line 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 <line 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 <line 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

Related Articles

Data Connector Import Rule fails to create association mappings
http://www.symantec.com/business/support/index?page=content&id=TECH191367

Import Rule fails to set or removes Asset Owner or Cost Center
http://www.symantec.com/business/support/index?page=content&id=TECH170991

Error "Row x skipped for data class '<data class name>'. Data class foreign key lookup on column '<column name>' failed." occurs when using a Data Connector import rule that has a foreign key data class mapping
http://www.symantec.com/business/support/index?page=content&id=TECH164571

Error "Error: 'name' argument cannot be null. Parameter name: name.'" occurs when trying to use a Data Connector rule that includes a foreign key
http://www.symantec.com/business/support/index?page=content&id=TECH178052

Error "Row x skipped for data class 'Identity'." occurs when using a Data Connector import rule to bring in resources with purchase order cost items
http://www.symantec.com/business/support/index?page=content&id=TECH166546

Data Connector Import Rule does not enable selecting Resource Name from the Resource lookup key
http://www.symantec.com/business/support/index?page=content&id=TECH193155

Exporting data to an Excel 2010 spreadsheet using a Data Connector Export Rule results in the error "There were 10 errors during the export of the first 10 rows of data."
http://www.symantec.com/business/support/index?page=content&id=TECH192633

Error "Unable to find column definitions in the given xml document." occurs when trying to use an .xml file with a Data Connector Data Source
http://www.symantec.com/business/support/index?page=content&id=TECH184046

Data Connector import rule fails to import fields as null when they are double quotes
http://www.symantec.com/business/support/index?page=content&id=TECH148276

Opening a Data Connector Import Rule times out or takes a long time to open
http://www.symantec.com/business/support/index?page=content&id=TECH192639

Error "Failed to load list of tables/sheets. The 'Microsoft.ACE.OLDEDB.12.0' provider is not registered on the local machine." occurs when trying to use Data Connector 7.1 with an Excel data source
http://www.symantec.com/business/support/index?page=content&id=TECH158045