Known Issues

This page lists important information about issues that apply to OL Connect 2026.1.2.

Script API setting changes in 2025.1

In OL Connect 2025.1 stricter checking was introduced for the Uniform Resource Identifier (URI) passed into the loadhtml, loadjson and loadtext scripting functions.
Special characters such as spaces in a path used to work but now need to be properly URI encoded.

Example:
// Worked in 2024.2 but not in 2025.1
var result = loadhtml("file:///C:/PPWorkDir/Hello World/Data/Example.html");
// 2025.1 onwards
var result = loadhtml("file:///C:/PPWorkDir/Hello%20World/Data/Example.html");

This applies to more than just the space character. Refer to RFC 2396 for the rules on URI encoding.

Email setting change in 2025.1

In OL Connect 2025.1, we fixed an issue where the “Do not inline styles” option would still inline CSS style rules on elements. This might affect existing jobs, particularly if you were inadvertently using the “Do not inline styles“ option but wanted the 'Apply CSS properties to elements’ behaviour.

Dynamic email attachments issue (updating from 2024.2.1)

Issues with Dynamic email attachments, which were added using custom scripts or via the Dynamic Attachment wizard.
The issue was that dynamic email attachments would accumulate across multiple messages. Additionally, when testing in the Designer application, this could cause attachments to be unintentionally added to the template.

As of 2024.2.2 we now ensure dynamic email attachments are handled correctly, with each email containing only the intended attachments and templates being saved properly.

If you are using dynamic attachments in your templates, we recommend testing them after updating to confirm that everything is functioning as expected.

Adding entries to manually added detail tables

The addRow() functionality did not work for detail tables that were manually added to the Data Model, prior to OL Connect version 2023.2. The fix for this issue allowed the use of addRow() for detail tables that are manually added to the data model or which have no extracted rows. As a result, any detail table without extracted data is now recognized as an existing but empty table, with a length of 0.

Remote translation files issue

Changes in a remote PO file (.rpo) are not shown in Preview mode or when double-clicking the .rpo file.
This will be addressed in a future release.

Performance not scaling as expected

When you have a machine with a lot of CPU cores and you configure Connect to run many Merge Engines (8+) simultaneously, the performance can be less than expected.
It has been reported that the CPU is not fully utilized and the performance per Merge Engines actually goes down, the more Merge Engines you add.

This will be addressed in a future release.

Unicode Variation Selectors issue

The Designer and Merge Engine can crash when a document or input data contains a Unicode Variation Selector. A variation selector is a special Unicode character in the range of U+FE00 - U+FE0F that indicates which variant of the previous character should be used.
The issue has so far only occurred on Windows 11 systems and will be fixed in a later release.

ODBC drivers do not all work with OL Connect

ODBC drivers do not all work with Java applications.
Since OL Connect is a Java application, it is strongly recommended you use JDBC instead.

Incorrect colors in print preview

Colors are not displayed correctly in previews generated by the Advanced Print Wizard.

Account permission issues

If you install and run OL Connect Designer and Server under different user accounts (for example, install under User1 and run Designer as User2), account permission issues may occur.

It is recommended that you install and use OL Connect Designer and Server under the same user account.

Issues converting some images from PCL to PDF

Problems have been reported with the conversion of some images, from PCL files to PDF output.
In some, the image is replaced with a grey box. In others, the images convert, but with a vertical line added to the edge of the image.

This is due to an issue with a third party library which will be addressed in a future release.

Incorrect warning when sending email from Designer

When sending email from the Designer with a license that allows this, an incorrect warning is displayed stating that sending email is not covered by the license. The warning does not prevent the emails from being sent.

Master Page not affected by style rules for <body>

In the output, content in Master Pages is affected by style rules targeting <html>, but not by style rules targeting the <body> element. This is because in the output, they are placed outside the <body> of the section to which they are applied. When editing a Master Page, style rules targeting the <body> element will work, because the Master Page is not currently applied to a section, but they will have no effect in the output.

Dynamic tables causing issues

In some specific circumstances the dynamic tables feature does not behave correctly. The following scenarios should be avoided to prevent subsequent issues with the template:

• Using page-break-before:always or break-before: always; on the top TR of a TBODY causes a problem and results in a pagination error

• It is possible to specify conflicting attributes on a TR element:

  • page-break-before:always or page-break-after:always combined with data-repeat

  • page-break-after:always combined with page-break-before:avoid on the next sibling TR (or similar combinations)

These issues will be addressed in a later OL Connect release.

DataMapper: Automatic Date/Time does not work with certain negative UTC time zone offsets

The new "Automatic" date parsing option in the DataMapper cannot parse dates with negative UTC time zone offsets of non-zero minutes.

For example: 2021-03-01T10:00-03:00 will work, but 2021-03-01T10:00-03:30 will not.

Positive time zones with non-zero minutes (such as +10:30) are unaffected.

The negative time zone offsets affected are: UTC -02:30; -03:30; -04:30 and -09:30

This issue will be fixed in a later release. In the meantime, the workaround is to use “Custom” or “ISO8601” date parsing options in DataMapper.

Print Wizard Preview showing some Landscape mode jobs in Portrait mode

Print jobs featuring associated Connect Output Presets which have Imposition options set to Landscape will not Preview in Landscape, but rather in Portrait mode. The printout is unaffected, however.

Issue after erroneous or incomplete update or re-installation

If one or more products (the OL Connect Designer, Connect Server, Software Activation, Print Manager, or Server Configuration Tool) or engines exit within a second of starting, this may be caused by a recent erroneous or incomplete uninstall before a reinstall or upgrade to a newer version of OL Connect.

This may be solved by deleting the %UserProfile%\Connect\.eclipse directory.

Backend database might require periodic maintenance

Databases maintain a variety of statistics in order to optimize performance. When high levels of inserts and/or deletions occur, the statistical data keeping can struggle to keep up. Over a period of prolonged and intensive processing this can result in a degradation in performance, with the whole database slowing down as it struggles to clean itself up.

In Connect terms the effect can be felt as the Data Mapper and/or Job Creation progressively slowing down.

To cure this issue, it is recommended that you periodically run manual maintenance on the backend database.

If using MySQL, the following script should be run in a query window:

set @a=null,@c=null,@b=concat("show tables where",
ifnull(concat(" `Tables_in_",database(),"` like '",@c,"' and"),''),
" (@a:=concat_ws(',',@a,`Tables_in_",database(),"`))");

Prepare `bd` from @b;
EXECUTE `bd`;
DEALLOCATE PREPARE `bd`;

set @a:=concat('optimize table ',@a);
PREPARE `sql` FROM @a;
EXECUTE `sql`;
DEALLOCATE PREPARE `sql`;

set @a=null,@b=null,@c=null;

If using Microsoft SQL Server run the following command in a query window:

sp_updatestats

Windows 10 Search service impacting Connect

The Windows 10 Search service runs as a background task, indexing files and folders. It has been noted that this background task is sometimes preventing files being added to the Connect temporary files folder when large amounts of files are being output and copied.

If this is an issue for you, we suggest disabling Search Indexing on the C:\Users\<username>\Connect folder.

This issue will be fixed in a later release.

Known Font issues

The following font(s) are known to have issues in OL Connect 2026.1:

• Benton Sans CFF font

Windows Server 2016 issue

As of OL Connect 2018.1 Connect is officially supported under Windows Server 2016.

Please note, however, that the Update Client application might be blocked by the enhanced security settings in Windows Server 2016.

To fix this, add http://updates.ca.objectiflune.com to the list of trusted web sites on that machine, or lower the internet access rules.

Limit of 100MB of image files within a single job

There is a limit of 100MBs for image files included within a single job. This allows most jobs to run faster. However, if a job requires more than 100MBs of image files, then the OL Connect image cache size can be increased. Please contact Support for instructions on how to modify the image memory cache value, if needed.

Memory usage in clustered environments

If Database Petitioning is not selected, then OL Connect can fill the database faster than the Clean-up service can clear it (the ratio is approximately 3:1), in high speed clustered environments. Therefore if the system needs to run for some time under a considerable load, a larger database should be used to prevent production from being interrupted. Or set the clean-up service to use Database Partitioning.

We also recommend only the Master Server performing the database clean-up, or the local Server Extension if the database is not installed with the Master, to maximize performance. For all Designers, Server and Server Extensions except one, set the clean-up of the database entities to run every 100 months and disable the clean-up for any Designer which also has a Server or Server Extension on that machine.
Note that if the Designer is a stand-alone then it is not connected to the central database for clean-up purposes.

The Database Petitioning option can be found in the Clean-up Service preferences.

Issues with Microsoft Edge browser

The Microsoft Edge browser fails to display web pages when the Workflow's CORS option (in the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future release.

Installation paths with multi-byte characters

When installing the Chinese (Traditional or Simplified) or Japanese versions of Connect, if the user specifies an alternative installation path containing multi-byte/wide-char characters it can break some of the links to the Connect-related shortcuts in the Start Menu and cause an error to appear at the end of the installer. The workaround for the moment is to use the default installation path. The problem will be addressed in a later release.

Switching languages

Changing the language using the Window > Preferences > Language Setting menu option does not currently change all of the strings in the application to the selected language. This is a known issue and will be fixed in a later release.

In the meantime we offer the following workaround for anyone who needs to change the language:

1. Go to the .ini files for the Designer and Server Config:
   • C:\Program Files\Objectif Lune\OL Connect\Connect Designer\Designer.ini
   • C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.ini
2. Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | ko | pt | tw | zh

Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up.

GoDaddy certificates

When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next. In some cases, however, this may not work correctly. For this reason those users should activate Place all certificates in the following store and then select the Trusted Root Certification Authorities as the target certificate store.

MySQL Compatibility

The minimum supported MySQL version is MySQL 5.6.

Available Printer Models

Note that only the single Printer Model (Generic PDF) will appear on the Advanced page of the Print Wizard by default.

To add additional printer models click on the settings button next to the Model selection entry box.

Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions.



For example the following printer types are actually identical:

• Generic PS LEVEL2 (DSC compliant)
• Generic PS LEVEL2 (DSC)

Color Model in Style Sheets

The color model of colors defined in a style sheet can sometimes change after editing the style sheet. This is a known issue and will be addressed in a subsequent release.

REST Calls for Remote Services

The Server will accept REST calls for all remote services and will make commands wait indefinitely until the required engines become available. The Server will log when it is waiting for an engine and when it becomes available. Note that there is no way to cancel any commands other than stopping the Server.

VIPP Output

Some templates set up with landscape orientation are being produced as portrait in VIPP. It can also sometimes be the case that text and images can be slightly displaced. These are known issues and will be addressed in a later release of Connect.

Magic Number changes when installing Docker

Installing Docker on a system where Connect has already been installed may impact Connect's licensing mechanism and require reactivation.

Note: Installing Connect after Docker has already been installed will not cause issues.