Skip to main content
This section documents export connector errors and Laserfiche activity errors that can be encountered during connector operation. This section also documents the possible causes of these errors, as well as ways to resolve them.

​
Export connector errors

The list below contains a description of the errors that may occur when exporting documents from FC to Laserfiche. These errors are recorded in the FC Processing Server Monitor log, as well as in the FC Administration and Monitoring Console (Event Log in the Processing Monitor tab).
  • System.Exception: System.IO.FileNotFoundException: Could not load file or assembly ‘Laserfiche.RepositoryAccess, Version=10.2.0.0, Culture=neutral, PublicKeyToken=3f98b3eaee6c16a6’ or one of its dependencies. The system cannot find the file specified. File name: ‘Laserfiche.RepositoryAccess, Version=10.2.0.0, Culture=neutral, PublicKeyToken=3f98b3eaee6c16a6’
  • Laserfiche SDK Runtime is not installed on the FC Processing station. Laserfiche SDK Runtime can be downloaded here: https://support.laserfiche.com.
  • System.Exception: Abbyy.Connectors.Dms.Infrastructure.DmsConnectorException: An error occurred while creating. Laserfiche.RepositoryAccess.LaserficheRepositoryException: A read-only session is not permitted to perform this operation. [9105]
  • Documents are being exported by a Laserfiche user that has the Only allow read-only access property enabled. To get rid of the restriction, follow the steps outlined in Parameters for connecting to the Laserfiche server.
    • The server-side Laserfiche license does not allow non-readonly actions (for example, a Retrieval license). Make sure that your license type allows you to perform the specified action. Information about your license can be found in the Laserfiche Administration Console when choosing a Laserfiche server.
  • System.Exception: Abbyy.Connectors.Dms.Infrastructure.DmsConnectorException: An error occurred while creating. Laserfiche.RepositoryAccess.AccessDeniedException: Access denied. [9013]
  • The Laserfiche user does not have the sufficient privileges to carry out the specified actions in the repository. Make sure that the user has sufficient privileges assigned.
  • System.Exception: Abbyy.Connectors.Dms.Infrastructure.DmsConnectorException: An error occurred while creating. Laserfiche.RepositoryAccess.ObjectNotFoundException: Volume not found. [9006]
  • A Default volume has not been assigned to the export folder in the Laserfiche repository. Open the repository using the Laserfiche client and check that the export destination folder, as well as all folders above it, have a Default volume specified. To do this, go to the Folder tab in the folder properties.

​
Laserfiche activity errors

The list below contains a description of errors that may occur when exporting documents from Laserfiche to FC for processing. These errors are recorded in the Laserfiche Workflow Designer log when launching a workflow (Messages tab).
  • Cannot export the document to FlexiCapture. Abbyy.Connectors.FlexiCaptureExport.FlexiCaptureExportException: Cannot open the session. System.Net.WebException: Unable to connect to the remote server
---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
  • This error may be caused by issues with the firewall. Check that the machines running the Laserfiche have permission to send requests to the machine running the FC Application Server (this includes its ports). By default, the FC Application Server uses port 80 (for HTTP) and port 443 (for HTTPS).
    • Make sure that access to the FC Application Server is set up for the protocol specified in the Server URL field, and that it is specified correctly.
  • Cannot export the document to FlexiCapture. Abbyy.Connectors.FlexiCaptureExport.FlexiCaptureExportException: Cannot open the session. System.Net.WebException: Unable to connect to the remote server 
---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
  • The FC Application Server cannot be found using the specified Server URL. Make sure that the address of the machine running the FC Application Server is specified correctly in the Server URL field.