Skip to main content

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

Article # 304467 - Page views: 98



Applies To

  • ERP System: Oracle, Peoplesoft, SAP
  • MarkView Version: 4.7 and higher


MarkView Scan is software that enables entering hard-copy documents such as receipts or invoices into the MarkView system. MarkView Scan also allows for the categorization of documents using barcodes, that can determine the type of document that the document is.

Troubleshooting Steps

If you encounter problems with MarkView Scan, please perform the following steps:

Scan station is not recognizing bar codes, all documents are displaying as "Uncategorized Document" or you are prompted to categorize the documents after scanning

  • From the MarkView Scan application confirm that the "Use Document Separators" menu item is selected in the Scan Menu. This option needs to be selected if you are using Barcode Coverpages between invoices
  • Confirm that the barcode coversheet that you are using was created in the same MarkView environment you are scanning into. For example a cover page from a test environment will not work in production.
  • Check to make sure that Barcode Recognition is enabled.
    To do this follow the steps below:
    1. In MarkView Scan select the Scan Menu --> Then Select Barcode setup.
    2. Check the box next to "Enable"
    3. In the Search Direction section, select all four (4) checkboxes.
    4. Ensure that Code 128 and Code 39(3 of 9) are in the "In Use" list in the lower right of the window.

Documents are unable to be viewed in MarkView

  • Ensure that you have the resolution set to 300 DPI, not any higher.
  • Confirm that you are scanning in Black & White, not in Color.

Documents do not upload to MarkView

Check/Troubleshoot file transport method


Enable Debug Logging

  • Locate your MarkView.ini file, The default location for this file is the Windows system directory, for example, C:\WINNT, and make a backup copy of this file.
  • In a text editor, open the MarkView.ini file.
  • Locate the parameter VerifyDocumentUpload, and set it to Yes, as shown below:
    • VerifyDocumentUpload_YesNo=Yes
      This causes the system to verify the existence of the file on the server after each document upload.
  • Locate the parameter FileUploadLog, and set it to a valid path name, for example:
    • FileUploadLogFile=C:\MarkView Scan\uploadlog.txt
      File upload verification information will be written to this log file. If this parameter is left blank, no verification information will be captured.
  • Save MarkView.ini and exit. MarkView Scan now logs scan activity.

Disable Debug Logging

  • In a text editor, open the MarkView.ini file.
  • Locate the parameter VerifyDocumentUpload, and set it to No, as shown below:
  • Locate the parameter FileUploadLog, and remove the path.
  • Save MarkView.ini and exit. MarkView Scan will not log scan activity.

Impact of Debug Logging

The scan log files generally do not grow very quickly and do not require a large amount of space. As turning on debug logging turns on file verification you may see a slight slow down in the speed of accepting your batches. This is caused by the extra error checking that is being done to ensure the file is successfully scanned and uploaded.

Keywords: diag, info