Frequently Asked Questions

eSight auto-import file storage issue
Last Updated 2 years ago

On large eSight systems where data is imported via CSV file using the auto import template feature, you may experience the following issue:

When eSight runs through an auto import, it scans a source folder for files. Typically this may be a folder that is where CSV files arrive viia CSV or are ripped from emails. When eSight successfully imports each of these files, it moves said files into its completed import folder at C:\eSightData\import\.

When dealing with systems performing many 1000's of imports a day, this folder quickly becomes filled with files. In a recent case, this folder contained 2.1 million CSV's going back 5 months. This causes the eSight data import process to stop working, even though all services appear to be running.

If the folder contains a huge number of files, you should rename the original 'import' folder to something else and let eSight create a new one itself. Data import should then resume immediately and you will see files being removed from the source folder and appearing in the new C:\eSightData\import\ folder.

A long term fix for this is for the customer to use a program or script that archives the files out of this folder and put them somewhere else, perhaps organised by date for later referral.

Please Wait!

Please wait... it will take a second!