Technical information

© 2013 by Omtool, Ltd. All rights reserved. Omtool, AccuRoute and the Company logo are trademarks of the Company. Trade names and trademarks of other companies appearing in this document are the property of their respective owners.
8-1Ricoh Embedded Software Architecture (ESA) Device Client v1.4 Installation and Integration Guide
Section 8: Troubleshooting
Section 8: Troubleshooting
This section includes:
Detecting workflow issues
(8-1)
Troubleshooting the delivery mechanism
(8-2)
Troubleshooting the message on the AccuRoute server
(8-2)
Troubleshooting the multifunction device
(8-4)
Complete these procedures in the order they appear. If you cannot resolve the issue, contact Omtool. (Go to
Omtool support and sales
on the inside front cover.)
Detecting workflow issues
After a document has been scanned on the device, the document should arrive at its destination momentarily but
can take up to several minutes when the server workload is high. If a document does not arrive at its destination
within a reasonable period of time, begin troubleshooting the environment. Omtool recommends troubleshooting
the workflow in reverse order because this is the easiest way to troubleshoot the setup on your own.
The easiest way to troubleshoot a workflow issue is to follow the document through the workflow in reverse order. When a
document does not arrive at its destination, troubleshooting starts with the delivery mechanism such as the mail server or DMS
application, and then continues to the AccuRoute server, the web server, and the device.
Figure 8-1: Troubleshooting the workflow in reverse order
To begin troubleshooting, go to Troubleshooting the delivery mechanism
(8-2).