Automatic import from a Hot Folder does not work

When importing automatically from a Hot Folder, import jobs are generated using a timer based on the settings specified in the project import profile. In general, import is carried out by Processing Stations under the account used to launch the Processing Station Windows service. For e-mail and FTP/SFTP import, the account specified in the import profile settings is used. If an error occurs during import, it is recorded in the job log for diagnostic purposes. The logs can be viewed in the Processing Server Monitor and in the Administration and Monitoring Console.

You should begin error analysis by checking that the Processing Server Monitor log properly records and displays job information. If some records are absent, check the following:

  • Verify that the Processing Server is running.
  • Verify that at least one Processing Station is running and that it is allowed to process import jobs.
  • Verify that automatic checking is enabled in the import profile of the project (i.e. that the “Check every x seconds” option is enabled and that a check interval is set).
  • Verify that a Hot Folder import profile is enabled for the project in /FlexiCapture12/monitoring/#Settings/Projects.

If a record for a job appears in the log but still an error occurs, check the diagnostic text. The following problems may occur when importing results:

  • Unable to establish a connection to the import source.
  • Unable to process the files.
  • Unable to load the files.

Unable to establish a connection to the import source

If the Processing Station is unable to get a reply from the import source, the log record will contain a message saying “Cannot connect to 'ServerName' (error code: 11001).” A full list of codes and what they mean can be found here:

For example, 11001 means that the specified name is not a known server name. This may occur due to a typing error in the server name. You should also check your firewall and proxy server settings.

The most common error that occurs when importing from a folder is “Access denied.”

Importing is done by the Processing Station. Depending on the import profile settings, the user account running the station should have:

  • Permission to access the source folder.
    When importing from a network folder, open the Sharing and Security tab in the Network Folder Properties dialog box and make sure that the user account used to run the Processing Station’s Windows service has full access to the folder.


  • Permission to connect to a remote e-mail/FTP server using the port that is specified in the settings. When importing from an e-mail server, the copy of Microsoft Outlook installed on the Processing Station should have the same bitness as the Processing Station. If Microsoft Outlook is not installed, the following message is displayed: “Cannot initialize MAPI: Microsoft Outlook is not installed.”

Important! When importing using the MAPI protocol, click-to-run Microsoft Outlook installation is not supported. In this case, the following error message is displayed: “Cannot initialize MAPI: Failed to create a class in the dynamic-link library Rs.MapiConnector.x86.dll.” 

Unable to process files when importing

If an error occurs when processing a particular file or e-mail message, please contact ABBYY’s technical support, providing them with the logs and the files that you attempted to import.

If an error occurs when converting Office documents:

  • Make sure that the Processing Station has the necessary Office conversion software installed.
  • If the conversion software is already installed, try using different conversion software.
  • Contact ABBYY’s technical support, providing the converter logs and the files that you attempted to import. The conversion software will be specified in the logs. Example error message: “Failed to open the file.'C:\ProgramData\ABBYY\Pop3HotFolder\ProcessingTasks\Task3752d11e\Email' using embedded Office application. Exit code: 4.”
  • If a description file was used for import, an invalid description file may be the cause of the error. Make sure that it satisfies the requirements set out here: Description file.

Unable to load files

This type of problem will result in an error message of the following type: ”Error connecting to 'http://AppServer', error code: (HTTP 503, 19, 0)'.” In this case, you will need to verify that the Application Server is available and is functioning properly.

10/9/2020 8:50:42 AM

Please leave your feedback about this article