Skip to main content
A timer generates import jobs from the settings in the project import profile. Processing Stations carry out the import, using the account that runs the Processing Station Windows service. Email and FTP/SFTP import instead use the account specified in the import profile settings. FlexiCapture records any import error in the job log. You can view the log in the Processing Server Monitor and in the Administration and Monitoring Console.

Check that jobs reach the log

Start by confirming that the Processing Server Monitor log records and displays job information. If records are missing, check each of these:
  • The Processing Server is running.
  • At least one Processing Station is running and is allowed to process import jobs.
  • Automatic checking is enabled in the project import profile, with the Check every x seconds option turned on and an interval set.
  • A Hot Folder import profile is enabled for the project on the /FlexiCapture12/monitoring/#Settings/Projects page.
If a job appears in the log but still fails, match the diagnostic text to one of the following.

Cannot connect to the import source

Cannot connect to 'ServerName' (for example, error code 11001) or Access denied.

Cannot process the files

An error processing a specific file, email message, or Office document conversion.

Cannot load the files

Error connecting to AppServer (for example, HTTP 503), so the Application Server may be unavailable.

Unable to establish a connection to the import source

When the Processing Station gets no reply from the import source, the log records Cannot connect to 'ServerName' (error code: 11001). Microsoft publishes the full code lists: Code 11001 means the specified name is not a known server name. A typing error in the server name is the usual cause. Check your firewall and proxy server settings as well. The most common error when importing from a folder is Access denied. The Processing Station performs the import, so the account running that station needs one of the following, depending on the import profile settings:
  • Access to the source folder – For a network folder, open the Sharing and Security tab of the Network Folder Properties dialog box. Give the account that runs the Processing Station’s Windows service full access.
  • Permission to connect to a remote email or FTP server – Use the port set in the import profile settings.
For email import, the copy of Microsoft Outlook on the Processing Station must have the same bitness as the station. If Outlook is missing, FlexiCapture reports Cannot initialize MAPI: Microsoft Outlook is not installed. A click-to-run installation reports Cannot initialize MAPI: Failed to create a class in the dynamic-link library Rs.MapiConnector.x86.dll.
MAPI import requires Microsoft Outlook 2016 in a non-click-to-run installation. Later Outlook versions and click-to-run installations are not supported.

Unable to process files when importing

If an error occurs on a particular file or email message, contact ABBYY technical support with the logs and the files you tried to import. If an error occurs while converting Office documents:
  • Make sure the Processing Station has the necessary Office conversion software installed.
  • If it is already installed, try different conversion software.
  • Contact ABBYY technical support with the converter logs and the files you tried to import. The logs name the conversion software. A typical message is Failed to open the file.'C:\ProgramData\ABBYY\Pop3HotFolder\ProcessingTasks\Task3752d11e\Email message.html.zip' using embedded Office application. Exit code: 4.
  • An invalid description file can also cause the error, if import used one. For more information, see Description file.

Unable to load files

This problem produces a message such as Error connecting to 'https://AppServer', error code: (HTTP 503, 19, 0)'. Verify that the Application Server is available and functioning properly.