Skip to main content
Kofax

MarkView Export Connector - Troubleshooting Guide

Summary

12245

 

Applies To

  • ERP System: All
  • MarkView Version: All

 

Overview

When export of batches from Kofax Capture to MarkView fail, the error associated with the failure can be discerned by processing the batch through the Kofax Capture Quality Control module as described in the following Support Article:

MarkView Export Connector- Obtaining the full error message when a MarkView Export Connector fails

 

Troubleshooting Steps:

If the problem is not described in the Known Errors below, try the following steps to see if they resolve the issue:

  1. Reboot the entire machine.
  2. Ensure the Import server, Kofax Capture and KTM services are restarted
  3. Check the Database account configured in the MVImportAPIConfig instance and make sure that it is unlocked.
  4. Check the configuration of the KCEC MarkView export connector for the affected batch class:
    • Open the Kofax Capture Administration console
    • Expand the relevant Batch Class
    • Right-click on the Document Class and select “Export Connectors”
    • In the list of assigned export connectors, select the Kofax Markview Export Connector
    • click on Setup.

If it is still not possible to identify the cause of the problem, open a support case and attach to it the following data:

  1. Screenshot of the error seen
  2. Description of the steps followed from the resolution steps above.
  3. DTM logs
  4. Kofax Capture / KTM logs
  5. Windows Application and System event log files from Kofax Capture machines (i.e. running Scan, Export, etc as appropriate for the particular problem). For problems related to KTM database files, the 170 MarkView event log is also necessary

 

 

Known Errors

 

Error# 1:

(401) Unauthorized.

Behavior

Error message:

 

Export Error: Script #1 (Markview Document) [0 MVImportAPI.MVImportException: Exception in HTTP Upload Request. ---> MarkView.DocServer.FileTransferException: Exception in HTTP Upload Request. -
--> System.Net.WebException: The remote server returned an error: (401) Unauthorized.

It can also show up as:

Error: Script #1 (MarkView Document EC) [0 MVImportAPI.MVImportException: Exception in HTTP Upload Request. ---> MarkView.DocServer.FileTransferException: Exception in HTTP Upload Request. ---> System.Net.WebException: The remote server ret...","0","0","0","0","0","0"

 

Known Causes

  • Incorrect MarkView username / password configured in the MVImportAPIConfig.
  • MarkView account configured in MVImportAPIConfig doesn’t have the required authorizations

Resolution

Error# 2:

(413) Request Entity Too Large.

Behavior

  1. Open the MVImportAPI Configuration page for each instance.
  2. Carefully re-enter the MarkView account information (Username and Password).
  3. To confirm that the user is authorized, try to login into Markview using the account.
  4. Ensure user is in Scan Users group.

Error message:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: Exception in HTTP Upload Request. ---> MarkView.DocServer.FileTransferException: Exception in HTTP Upload Request. -

--> System.Net.WebException: The remote server returned an error: (413) Request Entity Too Large.

Known Causes

The HTTP 413 “Request Entity Too Large” error indicates that the application server considers that the HTTP data stream sent by the client – i.e. the machine running Kofax Capture Export – was too large

Resolution

If you received this error, please open a support case and attach the following information::

  1. The error message.
  2. Apache log files.
  3. $ORACLE_HOME/Apache/Apache/conf/httpd.conf ( we need to check the value of “LimitRequestBody” parameter ).
Note: If you set the value of the parameter to 0, that will remove the restriction on the size.

Error# 3:

(500) Internal Server Error

Behavior

Error message is:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: Exception in HTTP Upload Request. --->

MarkView.DocServer.FileTransferException: Exception in HTTP Upload Request. -
--> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.

Known Causes

Incorrect permissions on the files or directories on the Document Server.

Resolution

  • Open a support case and attach to the case the DTM log file (mvdtm.log).
  • Attach to the case a screenshot of the error msg.

Error# 4:

The request was aborted: The request was canceled.

Behavior

Error message:

Error in document #1, 0 MVImportAPI.MVImportException: Exception in HTTP Upload Request. ---> MarkView.DocServer.FileTransferException: Exception in HTTP Upload Request. ---> System.Net.WebException: The request was aborted: The request was canceled.

Known Causes

Unable to access the volume path

Resolution

  • In the Support Tools “MarkView Preferences” output, check the “Volume Path Details” section.
  • Make sure that the scan machine can access the path assigned to the DTM path URL.
  • If you use HTTPS in the DTM URL or BIG IP setup, please open a support case indicating this and attach the error message you get to the case.

Error# 5:

MV_DOC_CREATION_USER_ID_FK constraint violated

Behavior

Error message:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: ORA-02291: integrity constraint (MARKVIEW.MV_DOC_CREATION_USER_ID_FK) violated - parent key not found ORA- 06512: at "MARKVIEW.MV_IMP_GENERIC", line 498

Known Causes

The user who ran the Kofax Capture Scan module, or the MarkView user configured in the MVImportAPIConfig instance did not match a MarkView UserID which was a member of the Scan Users user group.

Error# 6:

Incorrect date / time format

Behavior 

Error message:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: ORA-01843: not a valid month

Or …

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: ORA-01849: hour must be between 1 and 12

Known Causes

Incorrect time/date format issue on the scan station.

Resolution

Those errors happen usually when setting up a new scan station, you need to make sure that the date and time format configured on this scan station does match the format of the date and time of central site station (or any other working scan station).

Note: To check the date and time format: Go to Control Panel > Region & Language. Then, check the Date & Time format under the section “Date and time formats”.

Error# 7:

Invalid Workstation Serial Number

Behavior

Error message is:

Export Error: Script #2 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: ORA-20351: Invalid Workstation Serial Number …

Known Causes

Incorrect workstation serial number configured in the MVImportAPIConfig (the workstation serial number is case sensitive).

Resolution

  • This error indicates that the workstation serial number configured in the MVImportAPIConfig instance is incorrect, you need to reset it as it is configured in MarkView.
  • To see how the serial number is configured in MarkView, go to the Support Tools generate the preferences output, and have a look at the section “Volume Path Details”.
Note: The workstation serial number is case sensitive.

Error# 8:

Invalid username/password

Behavior

Error message:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 Oracle.DataAccess.Client.OracleException ORA- 1017: invalid username/password; logon denied

Known Causes

The MVImportAPI instance is configured with the wrong username or password to connect to the MarkView schema

Resolution

  • Open MVImportAPIConfig.exe, select the appropriate instance, and click the Preferences button. Confirm the Database User is correct and then re-enter the Database Password to ensure it is correct. Click the Test DB button and confirm that a Connection Success dialog box appears.

Error# 9:

(404) Not Found

Behavior

Error message is:

Export Error: Script #1 (Markview Document) [0 MVImportAPI.MVImportException: Exception in HTTP Upload Request. ---> MarkView.DocServer.FileTransferException: Exception in HTTP Upload Request. -

--> System.Net.WebException: The remote server returned an error: (404) Not Found.

Known Causes

The DTM deployment is not running on the Application Server.

Resolution

Make sure that the DTM deployment is up and running from Weblogic/OAS console.

Error# 10:

Invalid MarkView Process User ID

Behavior

Error message is:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: ORA-20891: MVT_Document_Capture.PostCreateDocument: ORA-20956: Invalid MarkView Process User ID (SYSTEM) supplied ORA-06512: at "MARKVIEW.MVT_DOCUMENT_CAPT...

Known Causes

The user name of the Scan operator in Kofax Capture does not match the name of a MarkView user who is a member of the SCAN USERS group.

Resolution

Error# 11:

Cannot insert NULL into MV_BATCH.BATCH_NUMBER

Behavior

Error message is:

Export Error: Script #1 (Kofax MarkView Export Connector) [0 MVImportAPI.MVImportException: ORA-01400: cannot insert NULL into ("MARKVIEW"."MV_BATCH"."BATCH_NUMBER")

OR

A-06512: at "MARKVIEW.MV_IMP_GENERIC", line 432

Known Causes

  • A batch number was not assigned to the batch when it was in the Scan queue.

Resolution

  • Open the Kofax Capture Admin console.
  • Expand the MarkView batch class.
  • Right-click on the Invoice Class and select "Database Validation".
  • Select the MarkView instance and click on "Properties" (It might take a while).
  • Re-enter the database connection details/password.
  • Create a new batch and try again.
  • For the existing batches, right click on them and select “Update batch class” then try to process them.

Error# 12:

Could not load file or assembly

Behavior

Error message is:

Export Error: Script #1 (Markview) [0 System.IO.FileLoadException: Could not load file or assembly 'MVImportAPI, Version=8.0.0.0, Culture=neutral, PublicKeyToken=f0c3df16e9a7b8ac' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Known Causes

  • Incorrect version of KCEC MarkView installed.
  • The issue could happen after a system upgrade.

Resolution

  • Install KCEC (the one that comes with the system package that you just upgraded to).
  • Install MVImportServer (the one that comes with the system package that you just upgraded to).
  • Republish the batch class.
  • Reboot the server and try again with a new batch.

Error# 13:

Bad Data

Behavior

Error message is:

Export Error: Script #1 (PRD) [0 System.Security.Cryptography.CryptographicException: Bad Data.

at Kofax.MarkViewExport.Retry.Execute(IRetry method, Int32 maxTries, TimeSpan timeWaitBetweenTries)

at Kofax.MarkViewExport.Retry.Execute(IRetry method)

at Kofax.MarkViewExport.RetryGetInstanceByName.GetInstanceByName(String instanceName)

at Kofax.MarkViewExport.MarkViewApi.GetNamedMarkViewInstance() at Kofax.MarkViewExport.MarkViewApi.GetMarkviewInstance()

at Kofax.MarkViewExport.MarkViewApi.ImportDocument(XmlDocument document, List`1 filelist)

at Kofax.MarkViewExport.Export.ExportConnector.ExportDoc() at Kofax.MarkViewExport.COM.KfxReleaseScript.ReleaseDoc()]

Known Causes

The error sometimes occurs after the installation of a Service Pack or Fix Pack.

Resolution

Re-run the MVImportAPIConfig.exe and re-enter the username and password for each instance.

Error# 14:

Out Of Memory, and FPS Color

Behavior

Batches fail to export with an "Out Of Memory" error that was preceded by "FPS Color" errors.

Resolution

Error# 15:

Unable to uninstall a prior version of the export connector.

Behavior

Installer hangs or displays an error when trying to uninstall the export conector.

Resolution

Error# 16:

Structural Errors appear in the MVImport Database

Behavior

Items fail to export with the following error message

Export Error: Script #1 (MarkView Beta) [0 MVImportAPI.MVImportException: ORA-20361: Structural errors appear in the MV Import database objects. Run MV_IMPORT_OBJ.VerifyObjects for details.
ORA-06512: at "MARKVIEW.MV_IMPORT", line 1046
ORA-06512: at line 4 ---> Oracle.DataAccess.Client.OracleException: ORA- 20361: Structural errors appear in the MV Import database objects. Run MV_IMPORT_OBJ.VerifyObjects for details.
ORA-06512: at "MARKVIEW.MV_IMPORT", line 1046
ORA-06512: at line 4

Resolution

Logging

  • The Kofax Log Collector utility is used to gather the Kofax Capture and KTM logs, as described in the following article:
    http://techsupport.kofax.com/knowledge-base/4844
  • It may, rarely, be necessary to gather the xml files that are exported from Kofax Capture. To do so, enable the KCEC Preserve Folder registry key to allow temporary XML files and image files to be retained after Kofax Capture Export as described in the following article:
    http://techsupport.kofax.com/knowledge-base/4929
  • To troubleshoot issues where the export fails in the MarkView DTM, it may be necessary to modify DTM logging as described in the following article:
    http://techsupport.kofax.com/knowledge-base/3976
  • To gather event logs:
    • Run eventvwr.msc
    • Right-click on the required log and select “Save Log As…” or “Save All Events As…”
    • Select *.evt or *.evtx as the log file format, enter a filename and click “Save”

Keywords: MVImportAPI, MVImportException