The below spreadsheet documents system errors encountered during the Smarteye/ Capture processes, along with detailed explanations and recommended actions for resolution:
Error in Logs | Details | Action from customer |
SmartEyeSAP/PRD/serrala/corecomp/fmcall/DOL/OCR_APINVOICE_DIRECT_POST Method: Post Headers/Parameters(name/data/type)HttpHeader Response Code: GatewayTimeout Response Content: Connection to the backend is timeout. Gateway Timeout Error Response Exception: | When attempting to transmit data to the customer's system (SAP), a timeout response is returned because the system is unable to receive the information within the expected timeframe. | Customer should extend the Timeout period on their system (SAP).After this Managed Automation can can try to retry the documents. |
RequestEntityTooLarge/Body Buffer Overflow | The document Capture/Smarteye is attempting to send to SAP exceeds the size limit accepted by the SAP system | The document should be processed manually, outside Smarteye/Capture. To address the issue permanently, the accepted file size limit should be increased in SAP. |
BadRequest Response Content: {"ERROR_CODE":"400","ERROR_MESSAGE":"Your request caused the called function module ARCHIV_CONNECTION_INSERT to raise exception ERROR_CONNECTIONTABLE","INFO_LINK":"HTTPS://qa.cloud:443/serrala/corecomp/fmcall?action=notes"} Response Exception | This message is a generic response to indicate there was an issue with the archiving of the document or the linking of an archived document to the SAP Object. | Whenever an error message such as “ARCHIVE_ERROR” or “ERROR_CONNECTIONTABLE” is received, we recommend to debug the SAP Function. In many cases, this error means that the content repository(ARCHIV_ID), the document archive ID(ARC_DOC_ID), SAP_OBJECT, AR_OBJECT or DOC_TYPE is incorrect. |
{ "ERROR_CODE": "500", "ERROR_MSG": "An exception of type 'CX_SY_CONVERSION_NO_NUMBER' occurred, that was not caught anywhere in the call hierarchy. It was not handled locally or declared using a RAISING clause.", "INFO_LINK": "HTTPS://cde.cloud:443/serrala/corecomp/fmcall?action=notes" } | CX_SY_CONVERSION_NO_NUMBER is a SAP ABAP runtime error that occurs when a program tries to convert a value into a number, but that value doesn't conform to the valid number formats. | This message is an error generated by SAP, therefore we recommend to reach out to the SAP basis or FS2AP team to further investigate and resolve the issue. |
Internal Server Error, with response content: An internal server error occured:for call: https://****-cpi-production.it-cpi005-rt.cfapps.eu20.hana.ondemand.com/http/transferRemittance | This error message is generated by the middleware (SAP System) and it typically indicates that something went wrong on the server side. | This message is an error generated by SAP, therefore we recommend to reach out to the SAP basis or IT to further investigate and resolve the issue. |
You have issues accessing the system HTTP POST on resource 'https://wmcloud.*****.com:33600/restv2/autobank/remmitance' failed: Remotely closed | The error message suggests that the remote server unexpectedly terminated the connection during the HTTP POST request. | This message is an error generated by SAP, therefore we recommend to reach out to the SAP basis or IT to further investigate and resolve the issue. |
InternalServerError, description: Internal Server Error, with response content: An internal server error occured: The MPL ID for the failed message is : AGNsdxb8YquZke7oG5O1uYfRBw1A | The Error message indicates that SAP encountered a server-side failure while processing a message. Here's what this typically means: Internal Server Error (500): Something went wrong during the execution of the integration flow, but the system couldn't handle it gracefully. | Using the MPL ID, reach out to the SAP Basis or IT to identify and resolve the issue. |
Unauthorized, description: Unauthorized, with response content: <html><head><title>Logon Error Message | SmartEye/Capture is not able to login to the host system | The customer is requested to verify the SAP credentials provided and inform Serrala of any updates. Once the credentials are updated, Managed Automation will proceed with reprocessing the documents |
Bad response code: RequestTimeout, description: Request Timeout, with response content: { | This issue indicates that the customer’s SAP system is returning a timeout response, likely because it is unable to receive the transmitted data within the expected timeframe. | The customer is advised to extend the timeout period in their SAP system. Once this adjustment is made, Managed Automation will attempt to reprocess the documents. |
Bad response code: InternalServerError, description: Internal Server Error, with response content: <?xml version="1.0" encoding="UTF-8"?> | This error message means that the server encountered an unexpected condition that prevented it from fulfilling the request. | This message is an error generated by SAP, therefore we recommend to reach out to the SAP basis or IT to further investigate and resolve the issue. |
Documents that failed in Conversion There is no JSON Response. No logs . | This issue happens when the documents are corrupted or password protected. | Unsupported document type which must be processed outside of SmartEye/Capture. Vendors should be advised to avoid sending password-protected or corrupted documents. |
Inner Exception: A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details. Original exception: AADSTS7000222: The provided client secret keys for app '********************' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: '******************** Correlation ID: '******************** Timestamp: 2024-04-16 05:29:21Z | The issue happens when the secret value has expired for the mailbox. | The customer must reach out to IT to provide Serrala with the updated secret value. |
The input string '' was not in a correct format. Stack Trace: at Syncfusion.Pdf.Parsing.PdfLoadedDocument.LoadDocument(Stream file) at Syncfusion.Pdf.Parsing.PdfLoadedDocument..ctor(Stream file, Boolean openAndRepair) at PDFTools.PDFDocument.OpenPDF(User user, MongoSettings mongoSettings, FileObject file) | Invoice PDF sent by customer/vendor is Damaged | The customer is requested to contact the vendor and ensure that corrupted PDF files are not sent to the Mailbox for processing. |
Can't open an encrypted document. The password is invalid. Stack Trace: at Syncfusion.Pdf.Parsing.PdfLoadedDocument.LoadDocument(Stream file) at Syncfusion.Pdf.Parsing.PdfLoadedDocument..ctor(Stream file, Boolean openAndRepair) at PDFTools.PDFDocument.OpenPDF(User user, MongoSettings mongoSettings, FileObject file) in C:\a\capture.core\capture.core\PDFTools\PDFDocument.cs:line 60 | Invoice PDF sent by customer/vendor is password protected | The customer is requested to contact the vendor and ensure that password protected PDF are not sent to the Mailbox for processing. |
HandleProcess returned false, putting task in error | Invoice sent by customer is Unsupported document type | Customer should not send the Unsupported document types . |