Asset Management

User Guide: Understanding Asset Import Logging

Overview

This User Guide will show you how to read the log files that are created when an Asset Import connector is synchronized in either Test or non-Test mode. It will show potential errors and warnings, how to prevent them, and tips to remember when importing csv files.

Related Articles

Prerequisites

  1. Create a folder to store the Asset Import Workflow Log
    • There is a recommended folder structure for SCSM and Asset Management in the Asset Management User Guides on the Cireson Portal.
    • You will want to sort by “Date modified” when looking at log files in this folder so you can see the most recent one at the top
  2. Enter the path for the log file in Asset Import settings
    • Administration > Settings
    • It is recommended to share out the folder(s) you will be using for log files to the SCSM Admins and the Workflow Account. Then enter the URL for the shared path. Save this path to your local computer since it will be viewed often.
  3. Optional: Download and Install a log reader program
    • It is possible to read the log files in notepad, but it will make it easier if you have a better way of filtering and finding any warnings or errors.
    • One tool to use is the Configuration Manager Trace Log Tool
    • It can be downloaded at http://www.microsoft.com/en-us/download/details.aspx?id=36213 
    • Please read and follow all licensing rules
    • The SCCM Toolkit will come with a tool names CM Trace. When you run it for the first time, it will ask if you want to use it as a default for logs.
    • Warnings will be highlighted in Yellow
    • Errors will be highlighted in Red

Once you have created the connector, and select “Synchronize Now”, you can open the log folder and watch the size of the log file increase as the data is importing.

Please run all connectors in “Test” mode and verify there are no Errors, and you understand the Warnings that are displayed before you actually import the data.

Basic Anatomy of a Log File (Beginning & End)

  1. Starting Import Workflow v7.5.3.0
    • This line will display the version of the Asset Import app when the connector was run
  2. Batch Size
    • In the Asset Import settings, the default size is 100.
    • You may change it for initial mass imports, but you should change it back.
    • You will get an error if you try to import more than that defined batch size.
  3. Running Connector in TEST mode
    • If the “Test Mode” checkbox is checked, you will see this line noting data is not being written to your database.
  4. Data source is CSV
    • Based on where the data was selected to import from, this will state it is from a CSV, SQL or ODBC source.
  5. Importing from…
    • This line will display where the data is being imported from
  6. Workflow completed
    • The final line will show how many lines were processed and how many errors
    • This count can be compared to the rows in the csv file or spreadsheet to verify that the correct amount of entries are going to be imported.

     

Standard Log Entries

These two examples are the only line items that should be displayed if there are no Warnings or Errors.

  1. Creating a value
    • Did not find an existing…
    • Created a new…
    • When a primary key value is not found, the next line will show it has been created

  2. Updating a value
    • Found existing …
    • Updated …
    • When a primary key value is found, the next line will show it has been updated

     

Possible Warnings, Errors, or Issues

This section will show common Warnings and Errors you may see. You should not continue with an import if there are errors. The warnings may only be informing you of values that are not populated if some entries have them and others don’t. After the example, you will be given a method to ensure they do not happen again and/or how to fix the issue.

  1. No warning or error will be displayed for this example, but you will see lots of created “” lines.

    • Reason: There are multiple rows of commas at the end of your .csv file
    • Prevent/Fix: Before you import a .csv file, open it and verify that there are no extra rows that look like this”,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,”. Delete them.

  2. Enumeration or List value was not found

    • Reason: When a value you provided for a list value was not found
    • Prevent/Fix: In the excel spreadsheet, verify all the values populated in the columns that have an “enum” data type, match exactly to the values populated in the Library > List that is associated to it. Make sure you examine the error carefully, because it could be something as simple as a preceding or following space that has been entered on a few of the list values in your spreadsheet.
    • The key word to look for in the Error is “Enumeration”

  3. Input String Error

    • Reason: You mapped a value to one of the 2 properties you are not supposed to use: Asset status, Object status
    • Prevent/Fix: Look at the Data mappings section of your connector and verify nothing is mapped to…
    • Reason: You mapped a value to a property that does not match the data type used by that field
    • Prevent/Fix: In the excel spreadsheet, make sure the data types match the values you have entered

  4. Missing or Moved .CSV File

    • Reason: The .csv file has been moved from the original location it was during the creation of the connector. Or, the .csv file is in a location the workflow account can no longer access.
    • Prevent/Fix: Don’t move the .csv file after creating the connector. Create a folder for all your .csv file to go into and do not change it.
    • Prevent/Fix: Place the .csv files on one of the Service Manager Management servers, or share out the folder to the workflow account.

  5. New column added to excel spreadsheet

    • Reason: You have added a new column to the csv file that does not match any property
    • Prevent/Fix: Delete any columns of data from the .csv file before you attempt to import it
    • Prevent/Fix: Extend the appropriate Asset Management class to include the new value

  6. Relationships are missing

    • Reason: You are importing Relationships, but some of the line items have blank values for the relationship.
    • Description: This warning is acceptable. You may not have or know the Custodian, or value for a relationship you are mapping for every entry. This is just letting you know some are missing.

     

1-to-Many Relationship Mapping Logs

The following will show what the log may look like when importing a one-to-many relationship property.

You will primarily want to verify that the Lines processed = Relationships created. This way you will know everything was configured correctly in the import connector and associated files and referenced files.

  1. The input file does not exist

    • Reason: The file has been renamed or moved.Â