Skip to main content
Kofax

MarkView All Components - Log File Locations

Summary

4844

Applies To:

  • ERP System: Oracle, SAP
  • MarkView Version: All Versions
  • Kofax Capture: All Versions supported by MarkView

Where can I find the MarkView log files in my environment?

The location of the log files is dependent on the specific MarkView component.

MarkView Installer and Verify

  • Log files for the MarkView Installer and Verify Utility can be found in the following directory:
    • <MV_INSTALL_DIRECTORY>\log
      • <MV_INSTALL_DIRECTORY> is the directory containing the MarkView Installation files

MarkView Middle Tier Application Server

  • OC4J Standalone ( MarkView Versions prior to 6.x )
    • <OC4J_HOME>/log
  • Oracle Application Server OAS
    • MarkView Application log files:
      • <ORACLE_HOME>/j2ee/<MV_INSTANCE>/log
        • <MV_INSTANCE> is the Oracle OC4J instance where the component is installed.
    • OAS Server log files:
      • $ORACLE_HOME/Apache/Apache/logs
        • $ORACLE_HOME/opmn/logs
  • WebLogic
    • MarkView Application log files:
      • MarkView 8.2 and lower
        • <DOMAIN_HOME>/log
          • <DOMAIN_HOME> is the home directory for the WebLogic Domain.
      • MarkView 9.0 and higher
        Note if no log files are found please check that the -Dmarkview.home argument is present in your WebLogic Server Start Parameters. This argument specifies where the MarkView log file base directory is located.
        • <MV_INSTALL_DIRECTORY>\log
          • <MV_INSTALL_DIRECTORY> is the directory containing the MarkView Installation files
    • WebLogic MarkView Server log files
      • <DOMAIN_HOME>/servers/<SERVER_NAME>/logs
        • <DOMAIN_HOME> is the home directory for the WebLogic Domain
        • <SERVER_NAME> is the name of the WebLogic Server where the MarkView components are installed.
    • WebLogic Admin Server log files:
      • <DOMAIN_HOME>/servers/AdminServer/logs
        • <DOMAIN_HOME> is the home directory for the WebLogic Domain
  • Wildfly and JBOSS (standalone and domain modes)
    • MarkView Application log files
      • <MV_INSTALL_DIRECTORY>\log
        Note if no log files are found please check that the -Dmarkview.home argument is present in your JBOSS_HOME/bin/standalone.conf file. This argument specifies where the MarkView log file base directory is located.
        • <MV_INSTALL_DIRECTORY> is the directory containing the MarkView Installation files
    • Wildfly Server and JBOSS Server log files
      • <JBOSS_HOME>/standalone/log (for standalone mode)
      • <JBOSS_HOME>/domain/log (for the host and process controller logs in domain mode)
      • <JBOSS_HOME>/domain/servers/<server_name>/log (for the server logs in domain mode)
        • Where <JBOSS_HOME> is the home directory for Wildfly or JBOSS
      • For instructions on enabling Access Log logging for Wildfly please see Article 13248.

MarkView Advisor Corda Server

  • <CORDA_INSTALL_PATH>/Server/logs
    • <CORDA_INSTALL_PATH> is the location of where the Corda Server is installed.
    • If you are unsure as to where Corda is installed please use the Support Diagnostic Tools to retrieve the version output and search for RESOURCE.CordaServerLocation.location. This Attribute contains the Corda Installation path.

Kofax Analytics for MarkView

  • WorkFlow Agent:
    • Please export the Application Event Viewer log file in EVTX format.
    • You can navigate to the event viewer by going to start-->Run -->eventvwr
  • WorkFlow Service:
    • Please export the Application Event Viewer log file in EVTX format.
    • You can navigate to the event viewer by going to start-->Run -->eventvwr
  • Insight Logs
    • All insight logs are stored in the C:\temp\<insight version> directory on the Insight Application Server.

Capture and Output Components

  • The Capture and Output Components which are installed as Windows Services ( Such as the Fax Server, Mail Gateway, and Bar Code Server) log directly to the Windows Event Viewer. MarkView File Capture logs directly to the Middle Tier Application Server log file.
    In order to view and save the Event Viewer log file please follow these instructions:
    1. From the machine where the Bar Code Server is installed go to Start -> Run
    2. Type in 'eventvwr.msc'
    3. On the left-hand pane, left click on the '170 MarkView' Application log file to view the log
    4. To save the log file right click on the '170 MarkView' Application log file and choose 'Save Log File As' enter a name in the File Name field and Save as Type: Event Log (*.evt)

Kofax Capture, KCNS and KTM

  • Kofax Capture Server:
    • Kofax Capture produces and error log file called ERR_yymm.txt and a batch log called log_yymm.txt - where yy is the last two digits of the year and mm is a two-digit number representing the month in which the information is logged.
    • For a Kofax Capture Server installation, the log files are located at:
      • \\<Server>\CaptureSV\Logs
      • Where <Server>represents the server name.
  • Kofax Capture Client:
    • The location of log files on a Kofax Capture client depends on the operating system.
    • For a Windows XP “Client” installation, the log is typically located at:
      • C:\Documents and Settings\All Users\Application Data\Kofax\Capture\Local\Logs
    • For a Windows Vista “Client” installation, the log file is typically located at:
      • C:\Users\All Users\Kofax\CaptureSV\Local\Logs
    • For a Windows 7 “Client” installation, the log file is typically located at:
      • C:\ProgramData\Kofax\CaptureSV\Local\Logs
    • For an Export related error please provide the full error message following the steps in the article below:
  • Kofax Transformation Module (KTM):
    • There are 3 sets of logs which should be gathered for troubleshooting KTM issues:
      1. The Kofax Capture ERR_yymm.txt logs (see the Kofax Capture section above).
      2. The KTM Server logs. These are located in the Local Logs folder for the machine running the KTM Extraction services. The log name is typically "KTM_yyyymmdd.txt", where yyyy represents the year, mm represents the month and dd represents the day on which the log is taken.
        • For a Windows XP “Client” installation, the log is typicallylocated at:
          • C:\Documents and Settings\All Users\Application Data\Kofax\Capture\Local\Logs
        • For a Windows Vista “Client” installation, the log file is located at:
          • C:\Users\All Users\Kofax\CaptureSV\Local\Logs
        • For a Windows 7 “Client” installation, the log file is located at:
          • C:\Documents and Settings\All Users\Application Data\Kofax\Capture\Local\Logs
      3. The KTM Validation logs. These are located in the temporary image folder: when a Batch is in progress and has gone through KTM Validation, there will be a KTM log in the temporary image path for that particular Batch running through the system. The typical log name is "KTMVAL_0000000A.log", where 0000000A represents the hexadecimal name of the Batch. Note that the batch folder - including the KTM Validation log - will be deleted when the batch is exported from Kofax Capture or deleted.
        • The typical path to find this log is:
          • \\<Server>\CaptureSV\Images\0000000A\Log
  • Kofax Capture Network Server:
    • Server Log Files
      • Information on KCN Server operations is stored in log files at the KCN Server.
      • Errors are logged from the KCN Service, and are sent to the ACISyymm.txt file (e.g. ACIS1205.txt) in the following location:
        • <Kofax Capture installation folder location>\logs\
      • Errors are also logged from the KCN Server, and are sent to the ACIWyymm.txt file (e.g. ACIW1205.txt) in the following location:
        • <KCN Server folder location>\logs\
    • Remote Site Log File
      • The client log file lists the activity between the remote site and the central site and is called ACICyym.txt (e.g. ACIC1205.txt)
      • This file is located in the same folder as the ERR_yymm.txt file on the Remote site machine.
  • Kofax Log Collector:
    • The Kofax Log Collector utility is attached to this article. This tool allows all relevant Kofax Capture, KTM and KCNS logs from a central site or remote site to be collected into a single .zip file.
      • Unzip Kofax Log Collector.Zip on the appropriate Kofax Capture machine.
      • Browse through the unzipped folders to find 3 files: "Kofax Log Collector.exe", "KofaxLogCollector.xml" and "ICSharpCode.SharpZipLib.dll"
      • Double click on "Kofax Log Collector.exe"
      • When the Kofax Log Collector window opens, ensure that "All Logs" is ticked.
      • Select File -> Export...
      • This will create a ZIP file in a folder called %TEMP%/1/KofaxLogCollector i.e. in the %TEMP% folder of the account which you use to run the collector.

Keywords: log