IBM Support

Error 'Index was outside the bounds of the array' when previewing CSV flat file import log report

Troubleshooting


Problem

User clicks 'Transfer - External Data - Import from Flat Files'. User selects import specification, import file (e.g. TXT file or CSV file) and clicks 'Run' button. After the import has finished, user receives the 'Statistics - Import of External Data' window. User highlights the import, and chooses 'preview' to see the import log. User receives error #1. User then clicks 'Transfer - Log Reports' then clicks 'External Data' tab. User highlights the most recent import (the one with the problem), and clicks 'preview'. User receives error #2.

Symptom

Error #1

Information
Standard Error
Source: C1.C1Preview.2
Description: Index was outside the bounds of the array.
OK

Error #2

Microsoft IE Execute shell
Microsoft IE Exceute shell has encountered a problem and needs to close.
We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.
[Debug] [Close]

Cause

There were too many errors (during the import) to view successfully.

TIP: Click 'Transfer - Log Reports' then click 'External Data' tab. Highlight the most recent import (the one with the problem) and look under the column 'Discarded Transactions'. You will see a huge number (for example 20000) rather than a more sensible number (for example 3 or 4).

Typically, the reason why there were such a huge number of discarded transactions was that something fundementally was wrong with the import, such as:

  • The wrong import specification was chosen
  • The import file (CSV/TXT) was corrupt
    • For example, it was formatted incorrectly (e.g. as an XLS file not a CSV file etc.)

Resolving The Problem

Correct the fundemental problems in your import, and re-try. Steps:One method of troubleshooting is to:

  1. Open the CSV file (for example in Excel)
  2. Delete 95% of the rows (to make the file much smaller)
  3. Re-save the CSV file
  4. Import

This will create a much smaller failure report, so (by assuming that the problem with the remaining 5% of data is the same as for the other 95% of data) you can locate the source of the problem.

[{"Product":{"code":"SS9S6B","label":"IBM Cognos Controller"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Controller","Platform":[{"code":"PF033","label":"Windows"}],"Version":"Controller (Frango) 8.3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Historical Number

1041689

Document Information

Modified date:
15 June 2018

UID

swg21367384