Skip to main content
Kofax

MarkView File Capture - What diagnostic steps should I follow and what information should I gather when there is an issue with MarkView File Capture?

Summary

4361

Applies To

  • ERP System: Oracle, SAP
  • MarkView Version (Oracle): MarkView 5.0 to 5.10.x and MarkView 6.2 and higher
  • MarkView Version (SAP): MarkView 6.1 and higher

Overview

MarkView File Capture (MVFC) is an automated email processor that enables users to submit documents such as invoices and expense reports as PDF or TIFF attachments to email messages. MVFC will continuously monitor the configured email accounts and when an email arrives in the designated inbox, MVFC processes the attachment into the appropriate MarkView workflow based on the bar code associated with the mailbox.

Troubleshooting Steps

If you encounter an issue with MarkView File Capture, please perform the following steps:

Verify the deployment is up

  • MarkView Versions 5.x to 5.10.x
    • MarkView File Capture runs in the same JVM as the Document Transport Module (DTM). To verify that the DTM is started and listening on the correct port, start a browser window and navigate to a URL of the following form, which should display a test page with information about the DTM:
      http://server:http_port/mvasdtm/markview?action=test
      In this example http_port will be the http port of the MarkView DTM which can be located in the Oracle Containers for J2EE (OC4J)_HOME\config-mvas- dtm\http-web-site.xml file.(If you are running https in your environment this will be located in the secure-web-site.xml file.)
  • MarkView Versions 6.x and higher
    • Log into Oracle Enterprise Manager or Weblogic Console and ensure that the "filecapture" component/deployment is running.

Review log files for errors

  • If MarkView File Capture is not functioning correctly then you will want to review the log files for any error messages. See the articlebelow for logging information
    • http://techsupport.kofax.com/knowledge-base/4844
    • If you have a memory related issue such as: java.lang.OutOfMemoryError: JVMXE006:OutOfMemoryError, this is an indication that the PDF attachment it was trying to convert was too large to be converted with the current JVM memory parameters. In order to convert a PDF to TIFF the entire PDF must be read into memory, and then as each page is converted to TIFF that memory is gradually

Check pre-requisite software

  • To check the versions of pre-requisite software please review the following Support Web Answer:

Emails are being sent however MarkView File Capture is not receiving them

  • If emails are being sent into MarkView File Capture however MarkView File Capture is not receiving them please review the following Support Web Answer:

End users do not receive success or failure notifications

  • If emails are processed successfully by MarkView File Capture however end users are not receiving success or failure notifications please review the following Support Web Answer:

Logging

Enable debug logging

  • Stop the File Capture OC4J( 5.10.x only)
  • To enable debug logging for MarkView File Capture set the MVFC_DEBUG_MODE preference to True.
  • Start the File Capture OC4J (5.10.x only)
  • For 6.X restart OAS or WebLogic,

Disable debug logging

  • Stop the File Capture OC4J
  • To disable debug logging for MarkView File Capture set the MVFC_DEBUG_MODE preference to False.
  • Restart OAS/WebLogic

Log file location

Impact of debug logging

Enabling debug logging on MarkView File Capture will cause the log file to grow at about 14 KB per one page document. Out of the box MarkView File Capture will let the log file grow to 5000KB and will keep 3 backup copies of the log file before overwriting them. In this case the maximum hard drive space taken up by the File Capture log file will be 20000KB. If the log file exceeds this size it will automatically overwrite the oldest information.

Keywords: mvfc, filecapture