Skip to main content
Kofax

Document Transport Module (DTM) - What diagnostic steps should I follow and what information should I gather when there is an issue with Document Transport Module (DTM)?

Summary

3976

Applies To

  • ERP System: Oracle, SAP
  • MarkView Version: All Versions

Overview

MarkView Document Transport Module (DTM) provides a secure means to transport images between the Document Server and your MarkView components.

For more information on the Document Server please see the following Support Article:

What diagnostic steps should I follow and what information should I gather when troubleshooting MarkView Document Server issues?

Troubleshooting Steps

If you encounter an issue with the MarkView Document Transport Module, please perform the following steps:

Verify the DTM is up

To verify that the DTM Application is running start a web browser 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

Review log files for errors

If the DTM is not functioning correctly then you will want to review the log files for any error messages. See the "Logging" section below for logging information.

Check pre-requisite software

To check the versions of pre-requisite software please review the following Support Article:
All MarkView Components - Supported versions of third party products

Unable to retrieve images

MarkView documents are stored as TIFF files in the Document Server file system. The pathnames of the TIFF files are stored in the MarkView database in a view named MV_PAGE_IMAGE_PATHS. Use the following procedure to determine the accuracy of the pathnames.

  1. Log into MarkView Administration as a user with Administrative rights and retrieve the System- Level value of the MVAS_DTM_WORKSTATION_SERIAL_NO preference (typically, MVAS_DTM_1).
  2. Run the following query for a sample DocumentID that you are unable to retrieve substituting the &workstation_serial_no value with the workstation serial number retrieved in Step 1 and the &document_id variable for the document_id that you are unable to retrieve.

select complete_filename
    from mv_page_image_paths pip, mv_workstation w
where w.platform_id = pip.platform_id
    and w.serial_number = '&workstation_serial_no'
and pip.document_id = &document_id;

  1. The value returned by the query in Step 2 is the location of the TIFF file. Once you have the location check the following items:
    • Does the directory exist?
    • If the directory does not exist then this is an indication that the Volume Paths may be incorrect.
    • Does the TIFF file exist?
    • If the TIFF file exists are you able to view the TIFF directly in a third party TIFF viewer?
    • If the TIFF file is viewable in a third party TIFF viewer was it scanned in Grayscale or Color? The MarkView Viewer Enterprise Edition and MarkView Express only support images scanned in Black and White.

Unable to upload images

The MarkView Capture and Output Components upload documents to the MarkView Document Server. Occasionally when uploading documents an error similar to the following may appear. (Note that the final status code may be different but the error will have a similar format.)

4/28/2004 4:29:13 PM: Error copying file
'f:\MarkView_Fax_Temp\BChannel1_33616888_20040427172923_1.tif' to
'http://server:port/mvasdtm/00000283.tif?
documentID=NULL&pageNumber=NULL&path=f:\170Systems\docserver\0\2\8\3\00000283.tif'.
Details: Error-2147221403: An error occurred during the attempted upload of 'http://server:port/mvasdtm/00000283.tif? documentID=NULL&pageNumber=NULL&path=f:\170Systems\docserver\0\2\8\3\00000283.tif'.
PutHttpFile DoPutHttpFile failed with HTTP status code 403.
  • Confirm the directory in the error message exists
  • The error message includes a directory and filename, (In the example above this is 'f:\170Systems\docserver\0\2\8\3\00000283.tif'). In order for the Capture and Output components to be able to write to this directory the directory must exist and be writeable by the OS user who is running the MarkView DTM.
  • Check MarkView privileges for the MarkView user which is configured in the Capture and Output components.
  • Each Capture and Output component is configurable with a specific MarkView UserID. In order to check the privileges for that MarkView UserID please review the following Support Article:

Errors on upload to Document Server

Logging

Enable Debug Logging

  • MarkView Versions 4.x to 5.5
    • Stop the DTM OC4J.
    • Open the Oracle Containers for J2EE (OC4J)_HOME\application- deployments\mvasdtm\mvasdtm\orion-web.xml file.
    • In the orion-web.xml file find the DTM_LOG_LEVEL parameter and set the value to 10
    • Start the DTM OC4J
  • MarkView Versions 5.10.1 to 8.0
    • To enable debug logging for the DTM set the MVAS_DTM_LOGGING_LEVEL preference to ALL.
    • Restart the Application Server, it is required for the logging changes to take effect.
  • MarkView Versions 8.1 and higher
    • To enable debug logging for the DTM set the MVAS_DTM_LOGGING_LEVEL preference to ALL.
    • With MarkView 8.1 and higher the logging changes will take place automatically within a few minutes, there is no restart of the Application Server needed.

Disable Debug Logging

  • MarkView Versions 4.x to 5.5
    • Stop the DTM OC4J.
    • Open the Oracle Containers for J2EE (OC4J)_HOME\application- deployments\mvasdtm\mvasdtm\orion-web.xml file.
    • In the orion-web.xml file find the DTM_LOG_LEVEL parameter and set the value to 1
    • Start the DTM OC4J
  • MarkView Versions 5.10.1 to 8.0
    • To disable debug logging for the DTM set the MVAS_DTM_LOGGING_LEVEL preference to WARN.
    • Restart the Application Server, it is required for the logging changes to take effect.
  • MarkView Versions 8.1 and higher
    • To disable debug logging for the DTM set the MVAS_DTM_LOGGING_LEVEL preference to WARN.
    • With MarkView 8.1 and higher the logging changes will take place automatically within a few minutes, there is no restart of the Application Server needed.

Log File Location

  • MarkView Versions 4.7 to 5.5
    • Article Number 000004844 -Title: All
      MarkView Components - Log File Location
    • File name(s): mvas-dtm*
  • MarkView Versions 5.10.x and higher
    • Article Number 000004844 -Title: All
      MarkView Components - Log File Locations
    • File name(s): mvas-dtm*,mvdtm.log
  • MarkView Versions 6.0 to 8.0
    • Article Number 000004844  -Title: All
      MarkView Components - Log File Location
    • File name(s): mvdtm.log
  • MarkView Versions 8.1 and higher
    • Article Number 000004844  -Title: All
      MarkView Components - Log File Location
    • File name(s): mvdtm.log

Impact of Debug Logging

  • Enabling debug logging on the DTM will cause the log file to grow at a rate of about 1KB per one page document. In versions of MarkView prior to 5.10.1 the log files should be monitored periodically to keep them to a manageable level. In MarkView 5.10.1 and higher the log file will grow to a size of 1000KB and will keep 2 backup copies of the log file before overwriting them. In this case the maximum hard drive space taken up by the DTM will be 3000KB. If the log file exceeds this size it will automatically overwrite the oldest information.

Keywords: troubleshoot MarkView Document Transport Module, troubleshooting, problem, general, minimum, information, 5.5, 887