Troubleshooting the auto-importer
The information in the article refers to:
Monitor-Pro MP-5
Applies to:
| Product: | MP-5 |
| Reported Version: | MP5.0.1 |
| Applies to: | All MP-5 versions |
| Area of effect | Importer |
Symptom
My file doesn't
move from it's to import folder
My file goes to
the Import Processor but is jumbled
My file goes to the "Not
Imported" folder
My file doesn't move from it's "to import" folder
Has it been working and stopped?
Do you have the file open in an application - maybe Excel?
Is this a new PC or setup and you can't get it working for the first time?
First ensure that the Auto Importer has been set up correctly. Follow the steps in kb_Auto_Importer_Configuration. If all is OK here then follow the following steps.
1. Eliminate the Scheduler.
Manually run the Importer (described in kb_Auto_Importer_Configuration). If it now works then you will need to troubleshoot the scheduler using Microsoft help.
2. Ensure that the Importer is looking at the correct database connection information.
In \Program Files\Monitor Pro\Monitor-Pro 5\Bin\importlogs you will find some
date stamped import logs. Open the most recent one. By default
Internet Explorer should open them. Failing this, use Notepad. They
look something like this...
- <IMPORTLOG DATE="20051130">
- <MSG VALUE="IMPORTER STARTED: C:\Program Files\Monitor Pro\Monitor-Pro
5\bin\Importer.exe" ID="1" TIME="11/30/2005 5:30:00 AM" TYPE="LOG">
<MSG VALUE="Unable to connect to database specified in: '/C:\Program
Files\Monitor Pro\Monitor-Pro 5\bin\Monitor Pro Database.mei" ID="2"
TIME="11/30/2005 5:30:01 AM" TYPE="LOG" />
The importer needs to look at the correct database to find your import template
(you could have many databases). This information is contained in a file called
MonitorEnterprise.mcl in \Program Files\Monitor Pro\Monitor-Pro 5\bin\. It
can be opened in notepad. It contains database connections as a list of .mei
files
Open any .mei files you have in /bin with notepad, and note which one points to
your database (will probably be called mp5_yourcompany.mei). Next, make sure
that the path in the .mcl file is exactly the same (to be sure copy & paste the
location from the address bar).
My file goes
to the Import Processor but is jumbled
Firstly ensure that your file is in the right format, and that you are placing
it into the correct "to import" folder. It is fairly easy to place for
example an mpr or columnar format file into the Std Variable (Crosstab) "To
Import" folder. If this happens you will see something similar to the
image below:
If this happens, reject the file and place it in the correct "To Import" folder.
My file goes to the "Not Imported" folder
Files that the importer cannot process go to the "Not Imported" folder. This could be for a number of reasons:
1. Non-data or non-supported files:
It stands to reason that e.g. a bitmap or other non-data file will not import.
The importer supports most text based formats automatically (the user does not
need to define them). These include .csv, .dat, .asc, .mpr, .txt and many
more. It does not support non-text based files so .doc, .pdf, .xls, .mdb
etc. Will all go to "Not Imported".
2. Supported file types but insufficient information:
The Importer can send data to the Import Processor only if it has sufficient
information about the data by means of column headers or hard-wired definitions
in the import template. Mandatory information is:
Site
Sample Point
Date
Variable
Data Source
Data Value
These may be spelled as above, or header aliases (stored in the database) can be used instead.
Files lacking the above information will go to "Not Imported".
Sometimes it may appear that your file has all of the above information but still did not import. One reason for this is if you have placed a crosstab file in the mpr folder. In this case the importer is looking for the name "Variable" in the header, which is not present in this format, and it will not be imported. Move the file to the correct import folder and try again.