2022.2
Table Of Contents
- Table of Contents
- What is Connect Send?
- Installation
- Printer driver
- Workflow Plugins
- Connect Send database cleanup service
- Moving Workflow to another machine
- Prerequisites
- System Requirements
- Installing OL Connect Send Printer Driver
- Printer driver properties and advanced settings
- Mass deployment of the OL Connect Send Printer Driver
- Using API Keys
- OLCS Notifier
- Known Issues
- Existing OL Connect Send Upgrade Issue
- Installing OL Connect Send on Windows Server 2016
- Installing OL Connect Send on a machine with Connect installed
- OL Connect Send issues under Microsoft Edge browser
- Printing PDF files with Adobe Acrobat Reader
- Paper Size vs Printer Page Size
- Passthrough Printing not supported
- License modes
- OL Connect Send in Workflow
- Using the Printer Driver
- Log files
- Troubleshooting
- OL Connect Send 2.1.2 Printer Driver Release Notes
- Overview
- Important Notes
- OL Connect Send 2.1.2 Printer Driver
- OL Connect Send 2.1.1 Printer Driver
- OL Connect Send 1.8.0 Printer Driver
- OL Connect Send 1.7.0 Printer Driver
- OL Connect Send 1.6.6 Printer Driver
- OL Connect Send 1.4.5 Printer Driver
- OL Connect Send 1.3.5 Printer Driver
- OL Connect Send 1.2.5 Printer Driver
Troubleshooting
There are some known issues that can be encountered when using Connect Send, depending
on the way OL Connect Send is installed, configured or used; see "Known Issues" on page39.
If another issue occurs and you find that you cannot solve the issue, there are a few things to
check.
1.
Switch the OL Connect Send Printer Driver logging to DEBUG. This can be done by
modifying the OL Connect Send Printer Driver; see "Installing OL Connect Send Printer
Driver" on page13. Then check the log files; see "Log files" on page69.
2.
Make sure that the OL Connect Send database service is running on the machine where
you have installed Workflow. The service is called OL Connect Send DBServer (the
internal service name is "OLCSServer").
3.
It has been seen, in some cases, that using two instances of the OL Connect Send Job
Processor plugin in different Workflow processes could lead to an error. Delete all the
processes using the Job Processor plugin and redo them from scratch. Please do not use
copy & paste. It is strongly recommended to use only one single process with the Job
Processor plugin and set this to “Self Replicating”. Any further processing can be
managed by the follow-up processes. Using two or more Job Processor plugins has been
known to cause an error when (re-)starting Workflow.
4. Sometimes, the license cannot be successfully activated due to the fact that the license file
is locked, blocked or under the control of a specific user account. In this case the Software
Activation Tool of Connect will show a message telling you that the license could not be
activated. The Software Activation Tool of Workflow will silently take note of this error
and close without displaying it. Please doublecheck if the license with the OLCS branch
has successfully been activated by reopening the Software Activation Tool and clicking
on the small i button. This will open the license overview window. A valid OLCS license will
have a respective entry at the end of the list. If this is not the case, the activation has failed.
In this case you need to activate manually by replacing the existing license file with the new
one:
a.
Rename the new license file with the OLCS enhancement to
OLConnect1.OLConnectLicense.
b.
Stop any Connect and Workflow services.
Page 72