Ricoh WES - Troubleshoot the WES

General troubleshooting rules

  • What? What procedure can be used to reproduce the incident?

  • When? What date and time did the incident occur?

  • Where? On which printer did the incident occur?

  • Who? On which user account did the incident occur?

  • Watchdoc.log: thank you for providing the Watchdoc.log file;a

  • config.xml file: thank you for providing the Watchdoc.log file;

  • server/device communication logs: please activate the trace files on each file.

 

Once this information has been gathered, you can send a resolution request from the Connect portal, the incident management tool dedicated to partners.

 

To obtain the best possible record of the data required for diagnosis, use the Watchdoc DiagTool® supplied with the Watchdoc installation program (cf. Creating a log report with DiagTool).

Scan, fax and photocopying are not in Watchdoc

If the scan, fax and photocopy jobs are not counted by Watchdoc, verify that the address (host name or IP) of the Watchdoc server configured in the device is correct:

  1. Iin the configuration interface of the queue, in the WES section, click on the button Application status (displayed when the WES is properly installed);

  2. Click the Download button to download the log files and WES configuration;

  3. In the downloaded .zip file, open the Config.json file using a text editor and check the information corresponding to the address of the server (Address) and ports;

  4. If the configuration of the address and / or ports is not correct, click on the Configure button on the queue configuration interface.

  5. Verify that the procedure has resolved the problem.

Activating WES Traces

To diagnose a problem with WES applications, you need to activate the log files specific to WES communications :

  1. in the Watchdoc web administration interface, from the Main Menu, Production section, click Printing queues, queues groups & pools;

  2. In the list of queues, click on the name of the queue with the WES for which you want to activate the trace files;

  3. in the queue management interface, click on Properties;

  4. in the WES section, click on the Edit the settings button:

  1. in the WES>Diagnostics section, tick the Enable traces box;

  2. in the Trace level list, select:

    • Auto: retains standard traces;

    • Include binary content: retains detailed traces.

  3. In the Path field, enter the path of the folder in which the trace files should be saved. If you leave the field blank, the trace files will be saved by default in the Watchdoc_install_dir/Logs/Wes_Traces/QueueId installation folder:


Activating the logs may slow down the server, so it is strongly recommended that you deactivate this option once the problem has been resolved.

Spool Transformation not taken into account – Oct. 2026

Context

As an administrator, I am configuring print job transformation (spool transformation) on the WES profile for Canon print devices. I have noticed that these transformations are not being applied.

 

Cause

This issue may be due to the driver configuration. The basic Canon driver incorporates the proprietary CPCA language, which is incompatible with job transformation. To enable this functionality, the driver must be configured to use the PCL6 standard.

 

Resolution

The device driver settings must be changed to ensure that it is PCL6-compatible rather than CPCA-compatible (see Prerequisites and prior configuration).

Quota duplication issue when printing in a large format (A3)

Context

When a dual quota system is enabled to account for different print formats (one quota for A4 and another for A3), an accounting error may occur, whereby large-format prints are counted twice against the quota.

For example, suppose we have:

  • a quota with a unit cost of €1 for an A4 print;

  • a quota with a unit cost of €2 for an A3 print.

When printing in A3, instead of being debited €2, the quota is debited €4.

 

Cause

The error is due to the device’s accounting system, which counts one large-format print as two small-format prints. The cost is therefore doubled, even though the quota configured for a large-format print is already higher than the quota for a small-format print.

 

Resolution

  1. Go to the print queue where the billing error was detected;

  2. from the queue view interface, click the ‘Edit queue properties’ button;

  3. in the ‘Print Queue Properties’ interface, go to the ‘Expert Mode’ section;

  4. for the ‘Accounting’ setting, tick the ‘Adjust accounting for large formats’ box:

     

  5. Start a large-format print job to check that the quota is no longer being counted twice.

 

N.B.: Once the issue has been resolved, if you find that the problem persists with colour printouts only, please update Watchdoc to version v.6.1.1.5696 or later, which includes a fix (for an even number of pages only).

WES can no longer find the output queue – Error message: “Unable to locate the output queue” - sept. 2026

Context

A print queue using the cross-server printing function is migrated from one server to another. After initiating a print job to this queue, the user attempting to unblock it is presented with the following error message: “Unable to locate the output queue” (see Troubleshooting WES). In the WES logs, the administrator finds the following message: “! WARN [...] WES|RestApi21Controller “Could not find target ‘Queue [Queue ID]’ in the local config. Any local job will be visible, but will not be able to print on that remote device!”.

 

Cause

The cache retains the identifier of the queue that has been migrated to a new server. Therefore, if the queue is accessed too soon after its migration, its identifier – which is associated with the old server – is still present in the cache, which has not had time to be cleared.

 

Resolution

You should restart the Watchdoc service to clear the cache. Then try printing again to check whether this has resolved the problem.

Renewal of the Access Token before expiration - New expiration date : 20280222

Context

When Watchdoc uses a Ricoh WES, it may occur that an alert message indicates that the access token will soon expire and invite you to contact your retailer:

 

Resolution

This issue can be resolved by one of the following operations:

  • by updating Watchdoc;

  • by making automatic changes using the PowerShell script (WatchdocRefreshRicohToken.zip) (to be applied to all servers in the domain, master and slaves);

    or

  • by making manual changes using the procedure outlined below (to be applied to all servers in the domain, master and slaves).

 

Procedure

Since this procedure requires a service interruption, be sure to perform it when it will have the least impact on printing activity. Depending on the size of your print fleet, this service interruption can take between 15 seconds and 20 minutes.

 

To modify the Watchdoc configuration file:

  1. log in to the server that hosts Watchdoc as an administrator and shut down the Watchdoc service;

  2. search the config.xml file (saved by default in C:\Program Files\Doxense\Watchdoc\Data\config.xml);

  3. copy the config. xml file to save it;

  4. open the config. xml with a text editor and seach the tag <ricoh-web-api>.

  5. If this tag doesn't exist, create it under the <instances><default-instance> tag;

    modify the tags included in this tag as follows:

 

<ricoh-web-api>

<remote>

<token>/yRUEU9p0bcbIoN5wA3BTxPAAITn+8LXqRCmNpzb7zGZZIacUXsvz1rEknxlb2yCgisDrak4lTi1EjQYncukK9cMwxi1jShy5fN9qCUy9HRdL8qIYr4mU6aQrJhVVUwE8sWIRaaZG/3aZA07ybuJvUEoTf/OA66ja2I8Cf+9N4oGvErB3D6ZZh3GJ+kYcUZ0</token>

<valid-until>20280222</valid-until>

</remote>

<browser>

<token>/yRUEU9p0bcbIoN5wA3BTxPAAITn+8LXqRCmNpzb7zGZZIacUXsvz1rEknxlb2yCgisDrak4lTi1EjQYncukK4cxmrZHgFOSkv7Yl2KGKSJhDL4Jw8dRfwat4g6pQkkV8sWIRaaZG/3aZA07ybuJvWtAIrYyDz2ZFxhihx/d5srA+yWYP6Sbn8dufT8VstpiMtpQC6O/rDX3/tY1jGK6jw==</token>

<valid-until>20280222</valid-until>

</browser>

</ricoh-web-api>

 

In the <token> tag, there must be no spaces in the character string;
if there are spaces, remove them.

 

  1. As in the following example:


 

5. save the config.xml file;

6. restart the Watchdoc service;

7. in the Watchdoc administration web site, check that the access token alert message no longer displays.

Unable to find the ‘Doxense.Web assembly, Version=5.4.0.0, culture=neutral, PublicKeyToken=94de63351b6ea861’.

Context

 

When the Ricoh WES is installed, the following error is displayed when the Configure button is clicked:
Unable to find the 'Doxense.Web Version=[n°_version], Culture=neutral, PublicKey Token=94de63351b6ea861'

 

Resolution

Install the Ricoh WES manually.

Do not use the WESRICOHDEPLOYER

 

Information to ask the technician

Have the login details for the print device's web portal.

Ask the technician on site to activate SP Modes and confirm as many times as possible using the hash key #.

  • 5-113- 002 = 0

  • 5-401-230 = 00000001

  • 5-401-240 = 1000

  • 5-420-041 = OFF

  • 5-490-001 = Allowed

WES Ricoh - Native Scan feature - Unable to scan a document - Scanner full log error message

Context

When using the native scanning functionality, an error message appears on the device screen: Full scanner log contact the administrator.

 

Cause

This message relates to scan log management on the device.

 

Resolution

  1. Using a browser, access the device configuration interface as an administrator.

  2. In the configuration interface, click on the Scanner menu item, then General Settings.

  3. For Print and delete scanner log, select: Do not print: delete oldest.