×
Menu
Index

13.5. Troubleshooting MFP Connect

 
Symptom
Check
No MFP Capture tab after installing
The MFP Connect setup was not run on this server, or it does not match the ChronoScan installation (32 vs 64 bit): uninstall it and run the other one. The ChronoScan license is PRO (MFP Connect needs Advanced or Enterprise).
Test connection fails
Device address and HTTPS option; administrator password; the device web interface opens from the server.
Register fails with an authentication error
Device date and time; the administrator password (a locked account after too many attempts).
Test connection or Register warns about the EIP version
The device is older than EIP 3.0: its browser cannot show the ChronoScan screens. The Machine information column shows the model and the EIP version the device reported.
Button missing on the device
Extensible Services Browser enabled; registration done; reboot the device.
Button opens but shows an error or nothing
The device cannot reach http://<server>:8580: firewall, server name resolution, service stopped. With a PRO license the device shows a license message.
Button opens but the screen stays empty: only a title and "Choose what you are scanning"
A device older than EIP 4.2 with a ChronoScan on the server that does not support its browser yet: update ChronoScan on the server. The screens are served by it, so there is nothing to do on the device.
Machine marked "(different from current)"
The server URL changed after the registration: click Register again on that machine.
No configurations on the device, or an old list
The configuration is restricted to other machines (Available on all machines unchecked); the forms are regenerated when a configuration is saved.
A value is refused on the device
The job's rule for that field: required, validation mask, value list. The message on the screen gives the reason.
"Scan error" on the device screen
The device refused the scan job: the reason it gives (its SOAP fault) is shown on the screen, in the Generated batches row (state ERROR) and in the MFP Service Activity log. Send it to support if it is not obvious. The reason InvalidURL on an AltaLink means a ChronoScan build older than this chapter: update ChronoScan on the server. A device older than EIP 4.1 scans through its older scan service ("Scan V2" in the reason): send the reason together with the model and EIP version that Test connection shows.
A value list is empty ("No matches")
The list has no values for this job: check the value lists of the job and their database connection in ChronoScan. Changes take up to a minute to reach the devices.
Scan done but no batch appears
Service status line in ChronoScan; the MFP Service Activity log at the bottom of the tab.
Batch created but not processed
Hot folder engine running; the job's processing operations configured (Processing/Export Options).
Logs and files
Everything of MFP Connect is kept in the ChronoMFP folder of the ChronoScan configuration directory (the service is registered on that directory):
File
Content
mfp_config.json
Machines (with the administrator password encrypted), capture configurations and settings. Edited from the MFP Capture tab.
mfp_forms.json
The forms served to the devices, regenerated by ChronoScan whenever a configuration is saved.
mfp.activity.log
The activity of the service: registrations, scan sessions, batches created, errors. Shown in the MFP Service Activity list.
mfp.batches.log
One line per state change of each scan. The Batches generated list is built from it.
pending\
The queue for the hot folder engine: one file per batch waiting to be processed. Empty when everything is processed.
Received files
The scan file and the index data of each session, named by the session token.