Document Recovery Guidance

This document provides guidance on recovering documents from issues that are misconfiguration, system, or third-party related for Input Management, where the system might not be able to process them to on-premise.

Documents in Faulty lane (Fehlerhafte Dokumente)

If documents cannot be processed through the cloud due to a non-transient error, they might end up in Fehlerhafte Dokumente. You can access them in [(https://.stp-cloud.de/im/clickworkingv2/#/document/faulty-documents)]. In such cases, please follow these steps:

  • Check the Kommentar column for the error location

  • Click the triangle icon Es ist ein Fehler bei der Verarbeitung aufgetreten to review the error message and to determine if it is a known issue

  • If the failure is caused by a system or third-party error, click on download icon Dokument herunterladen to retrieve the document

  • Wait for a notification on the bell icon and click to download the zip folder containing all generated files

  • Navigate to your download folder, extract the files and copy the original0000.<file_type>

  • Get access to on-premise system

  • Check the destination folder where the documents should be placed after successful processing and paste the extracted file there

  • If the issue is new or unknown, create a ticket and/or contact a support agent

  • If the failure is caused by misconfiguration, fix the configuration and click on redo arrow icon Erneut Verarbeiten to reprocess the document

Common Error Types by Kommentar

Image Rendering

Ususally a third-party error. A known issue in the Aspose library prevents it from recognizing certain fonts in the document. To verify if this is the case, please check the Processing Error Details:

  • Message for this type of the error is “This error is probably caused by a corrupt or invalid PDF file handed to Aspose.PDF”.
  • StackTraceString usually contains “SelectFont” as text inside.
  • Source is “Aspose.PDF”.
Export to on-premise system

Usually an error due to a misconfiguration. This error often happens when a document is exported to on-premise system with no proper settings set. Possible reasons include:

  • Export without an assignment when it is required.
  • Export without an external system configured.

To verify if this is the case, please check the Processing Error Details:

  • Message: “DmsConverter: Could not find DMS configuration . Candidates are: ”.
  • Source is “STP.IM.OutputMapping”.

Another common error is due to a failure in on-premise. This error occurs when the document export fails due to a non-functional connector (STP.IM.LEXolutionDmsConnect) The issue needs to be fixed first. To verify if this is the case, please check the Processing Error Details:

  • Message: “Error while importing document to DMS. Please check LEXolutionDmsConnectOnPremiseService logs!”.

Documents in Processing (Ohne Klasse)

If documents cannot be processed through the cloud due to an error, they might also end up in processing Ohne Klasse. In such cases, if you are not in TenantAdministrator role, please contact a support agent, otherwise follow the steps:

  • Open the document in Ohne Klasse
  • Click on the download icon Dokument herunterladen to retrieve the document
  • Wait for a notification on the bell icon and click to download the zip folder containing all generated files
  • Navigate to your download folder, extract the files and copy the original0000.<file_type>
  • Get access to on-premise system
  • Check the destination folder where the documents should be placed after successful processing and paste the extracted file there