Troubleshooting the File Collector

Important: You do not have the latest version of Historian! You are missing out on the newest capabilities and enhanced security. For information on all the latest features, see the Historian product page. For more information on upgrades, contact your GE Digital sales agent or e-mail GE Digital Sales Support. For the most up-to-date documentation, go here.

If you are experiencing any problems with the File Collector, use the .LOG file (in the \LogFiles folder) to troubleshoot. The .LOG file sometimes logs errors that do not get processed to the Historian Administrator. For example, if you have no archives in your system and you attempt to import a .CSV file with formatting errors, the file is not processed and no alerts are sent to the Historian Administrator (if there are no archives created, the message database has not been created). But this error does appear in the .LOG file.

The following table lists typical Error messages received with the File Collector and tips to troubleshoot those messages.

Typical Error Messages and Suggested Solutions

Error Message Troubleshoot by...

12-Aug-0113:38:00 - Import Line Error: Input past end of file

12-Aug-0113:38:00 - Error Occurred On Line12: General Format Error

 There is an extra line in the file. Open the file in Note- pad and remove the extra line.

10-Aug-01 15:47:02 - Import Line Error: Type mismatch

10-Aug-01 15:47:02 - Error Occurred On Line 2: General Format Error

 Two fields were rolled into one due to a missing comma. Open the file in Notepad and add the comma.

12-Aug-01 14:18:12 - Invalid Import Field: TimeResolution

12-Aug-01 14:18:12 - zProcessFragment>> Aborted Import Due To Formatting Errors

If an import field is invalid, (in this case Time resolution should be StoreMilliseconds) the import will abort.

Identifying Lines in which an Error Occurs

If the File Collector log file contains an error description such as:

20-Jul-01 10:1717 - Import Line Error: Input past end of file

20-Jul-01 10:1717 - Error occurred on Line 7:Geneal Format Error

the line number in the log is produced by the SDK, not the File Collector. This means that the line number is counted relative to the header or field list for each section of the file, ignoring comments and blank lines.

CSV File Imports

If a .CSV file has an extra line in it, it may not successfully import using the File Collector. If a .CSV file has extra commas on the data line, it may not import completely.

Typically, a .CSV file must be less than 10 MB and an ideal file should be 1 or 2 MB. If the file size is greater, then the File Collector may not respond.

If you view these files through Microsoft Excel, the characters are not visible. It is recommended that you use a text editor to examine files that are causing format errors when you attempt to import them.

You cannot import CSV or XML data that goes back beyond the Archive Active Hours setting (1 month by default). Adjust your Archive Active Hours setting and re-import the data.

Also, data before the first archive will not be imported.

Troubleshooting Large File Import

To prevent a locked file scenario when building large files for import into the Incoming directory, first build the file under a temporary file name or directory that will be ignored by the File Collector, then rename or move the file to the real file name or Import directory when the file is fully built.