Firewall issues
A firewall protects the computer or the network and allows incoming connections from limited access points only when certain rules are followed. The firewall rejects all data that does not conform to its policies, which are set by the firewall administrator. In order to stop your firewall from blocking ABBYY FlexiCapture Cloud from accessing the user’s resources, you need to correctly set up your firewall rules, regardless of the import type that you are using. For more information about this, see Import security features in ABBYY FlexiCapture Cloud section.Network issues
If network issues or issues with the secure SSL/TLS connection arise, we recommend that you contact your organization’s local network administrator.IMAP issues
For importing documents to ABBYY FlexiCapture Cloud from e-mails using the IMAP server (outlook.office365.com), a Hot Folder image import profile is used. Each import profile is assigned to a single e-mail account. When importing files via e-mail, problems with user account details often arise. To solve these issues, check the following:- Verify that you are using the correct password for the e-mail account.
- Make sure that the e-mail account that you are importing messages from works.
ABBYY FlexiCapture Connect issues
When importing files using ABBYY FlexiCapture Connect, you may encounter a code 403 error returned by the IIS service. The cause of this type of error may be the incorrect assignment of roles to the user account that was used to configure ABBYY FlexiCapture Connect. To be able to import documents, the user account should be set up as an External User. For more information, see Setting up user roles and access rights. If the cause of the problem is not known, you can try inspecting the ABBYY FlexiCapture Connect service logs in Event Viewer. To collect a log file, do the following:- Repeat the import attempt
- Navigate to Control Panel > Administrative Tools > Event Viewer
- Select Windows Logs
- Select Application and view the logs.
Event log
You can view the event log and check the Administration and Monitoring Console error logs. For more details on how to do so, see Processing error diagnostics.If the import is unsuccessful, the processing batch may not have been created yet, which is why you do not need to filter your search by batch name when viewing the Event Log, and only view those events that contain errors instead.
