Skip to main content
Kofax

Device Web Service - How to capture trace logs

  1. Last updated
  2. Save as PDF

Information:

DWS is used with AutoStore, Equitrac Office 5.x, Equitrac Express,and Output Manager, when deploying embedded clients, including the Nuance Unified Client.

DWS logs are collected via the DWS web page, and not through the AutoStore Process Designer, Equitrac System Manager, or Output Manager Console.

Connect to https://<DWS-IP address>:8443/DwsMain/WebAdmin/

  • Where <DWS-IP address> is the IP Address of the DWS server.
  • The URL is case sensitive, so D, M, W, and A must be upper case and the rest lower case.
  • Make sure that the last character of the URL is /.  If this is missing, a "HTTP Status 404" error may result.
  • Log in with the service account used with the server software (AutoStore, Equitrac or Output Manager) or a user who is a member of the local Administrators group.

The following should be done.  See below for details and hints on how to perform the steps.

  1. Clear all logs
  2. Enable all logs
  3. Reproduce to gather logs
  4. Create and Save the Snapshot
  5. Disable all logs
  6. Document the steps, environment, and symptoms
  7. Send the zip file, together with information gathered in step 6, to Nuance Support
  8. Search for Dws.log under: %appdata%\..\Local\Equitrac\Equitrac Platform Component\EQDWSSrv\webserver\webapps\DwsMain\WEB-INF\felix-cache , collect those files and send to Nuance Support 

(Steps 1, 2 and 5)

On the "Logs" tab, the available logs and their sizes can be seen. On the right-hand column of each log, individual log can be cleared, and also to disable or enable it. If the Enable column shows the word "Disable", that means currently the logging is enabled. The option for "Enable all logs", "Disable all logs" or "Clear all logs" are available on this tab.

(Step 4)

On the "Snapshots" tab, complete the required information and click "Create" to collect all the logs into one zip file.

NOTE:

DWS has logging enabled for the first 5 minutes after the service starts, regardless of whether logging is enabled or not - this is to aid in service start-up or connectivity issues.