1.6

Known Issues
Installing OL Connect Send on a machine with Connect
installed
When OL Connect Send plugins are installed (either via the pre-release of Connect Send or via
a Workflow installation) on the same machine as Connect, an interference between OL
Connect Send's internal database and that of Connect may occur, causing the browser popup
to be blocked.
This issue can be fixed by applying a startup wait to the Connect Server Service. If the issue
occurs during runtime, restarting the Connect Server Service will fix the issue.
OL Connect Send issues under Microsoft Edge browser
1. Issues with using the built-in Windows 10 default "Administrator" account and the OL
Connect Send Client. This is due to Windows disallowing the opening an Edge browser
whilst running under this account. This blocks interaction with the printer driver.
2. The Microsoft Edge browser fails to display web pages when Workflow's CORS option (in
the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future
release.
Printing PDF files with Adobe Acrobat Reader
It is recommended not to use Adobe Acrobat reader to print PDF files with OL Connect Send.
Print the source file (e.g. the Word file) whenever available. If PDF files are to be printed with
OL Connect Send, use a different PDF viewer instead.
Adobe Acrobat Reader produces its own PostScript file, rather than passing the PDF to the
OLCS Printer Driver to generate a PostScript file. This doesn't hinder the transfer of the file, but
Adobe Acrobat Reader's own PostScript file sometimes lacks information about the original
PDF, which may cause errors in the processing of that file and in the interaction following the
transfer.
One known issue is that if the PDF contains a PostScript font (Type 1 in Adobe Acrobat
Reader), an "error retrieving character data” may occur in Workflow's Execute Data Mapping
Page 29