Watchdoc Print Client for Windows - Troubleshoot

Collect diagnostic files

In the event of a malfunction on WPC for Windows, it is possible to collect the diagnostic files to facilitate diagnosis,

  1. From the workstation where WPC for Windows is installed, right-click on the WPC icon ;

  2. in the menu, click Collect diagnostic files ;

  1. Click on the message informing you that the diagnostic files have been collected:

  1. This will take you to the download folder,where you will find a WPC folder containing the diagnostic files.

Accessing log files

To access the WPC for Windows trace files,

  1. access the Watchdoc server as an administrator

  2. go to the folder C:\Program Files\Doxense\Watchdoc Print Client\Logs.

Description of the folder content

In this folder

  • WatchdocPrintClientService.log contains the WPC Windows service logs.

  • WatchdocPrintClientGUI_x.log contains the application logs. The suffix (x in our example) corresponds to the Windows session identifier.

  • winspool_PRT_...log contains the supervision information for a print queue.

  • PortMonitor.logcontains traces of port monitor activity.

 

WPC for Windows. Drop in server performance

Context

There is a drop in server performance when WPC for Windows is installed on a large number of workstations.

 

Cause

This problem may be due to the number of ICMPClosed Internet Control Message Protocol is a network layer protocol (No. 3 in the OSI model) that controls transmission errors. In this way, a sending machine knows that there has been a network incident, for example when a service or host is unreachable. The Ping command is an example of an application that uses ICMP control messages. (Source : Wikipedia) requests sent from workstations to the server in the event of malfunctions, causing the server to become saturated.

 

Resolution

To resolve this problem, it may be useful to disable ICMP in the WPC for Windows configuration (see Configuring WPC for Windows) and check whether this improves server performance.

Driver print processor management

Context

When a user installs a print device using WPC for Windows, it is assigned the winprint Print Processor by default.

As a result, users may lose certain parameters defined by default with a print processor specific to my printing devices (watermark management, for example).

 

Cause

This behaviour is linked to the parameter defining ‘winprint’ as the default print processor when a printing device is installed via WPC for Windows.

 

Resolution

To resolve this issue, the desired Print Processor should be set when configuring WPC for Windows (see Configuring WPC for Windows, Windows section, Driver Print Processor setting).