ABBYY Flexi Capture - Email Import Failure - Exchange Folder Is Not Accessible

ABBYY Email Import not working

Customer reported that the email import was not importing anything for a specific email inbox. 

After looking into the task logs on the Processing Server Monitor we reported the following error message.

Exchange folder '/Inbox/ABBYY Import' is inaccessible.

This could be caused by a few different things.
  1. The username or password is incorrect for the email import.
  2. The exchange server the import is configured for is unavailable.
  3. The folder in the mailbox has been deleted or the name of the folder was changed in Outlook.

To determine the cause of the issue try logging into Outlook with the credentials provided. This help show that the issue lies outside of ABBYY FC.
  1. If you receive an authentication error you can assume that the login credentials provided are no longer valid.
  2. If you can log in, make sure that the folder that ABBYY is pointed to is still available. If not please update the folder name or add the folder that the import configuration is pointing to.

    • Related Articles

    • Mailbox Importer has stopped working

      DescriptionMailbox Importer has stopped working. [3/27/2019 1:11:09 PM] No configured accounts were found. Please check configuration to verify account settings are correct. ResolutionAfter revoking the Encryption Key, Starting the service to create ...

    • Scan Queue Scheduled Sweep not working

      Customer was looking as to why a Schedule job was not working. After adding the correct switch (-SCHED) all is working now.

    • Issue with Destop app (email)

      See attached documents and article...workaround performed on Customers  workstation resolved issue until switchover to https:// chrome://flags/#unsafely-treat-insecure-origin-as-secure ​

    • When attempting to import a license certificate, OnBase Configuration closes unexpectedly

      OnBase Configuration closes unexpectedly when attempting to import a new license certificate if the MSXML Parser 4.0 is not installed. Once installed, it should then be possible to import license certificates without further issue.

    • Invalid local-part at offset 0 from a Workflow Email Send step.

      Behavior: When workflow attempts to send an email, the step faults and shows the following error message; "Invalid local-part at offset 0." Solution: This error message occurs when an invalid email address has been provided. Please review the email ...