2022.2

Table Of Contents
In the meantime Objectif Lune would like to apologize to any customers affected by this problem and for
any inconvenience caused. For more information, please contact your local support team.
Data Repository error
The Push to Repository task, as well as the corresponding repository API calls SetValue() and
SetValueW() may on rare occasions fail with an unexpected error (517), caused by the Write Ahead
Logging (WAL) journal mode.
The workaround is to disable WAL journal mode:
1. Create the "Repository" key in \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Objectif
Lune\PlanetSuite\PlanetWatch\8.0\ if it does not exist.
2. Add a new DWORD32 value in Repository key named SQliteWALJournalMode and set it to 0.
Switching the registry key from 1 (WAL) to 0 (DELETE) disables the Write Ahead Log.
3. If the Write Ahead Log is disabled, -sham and -wal files should no longer appear in the Repos-
itory folder.
4. Restart the PPWatch service.
Other known issues
l
Custom plugins cannot be permanently removed from the Plug-In Bar through the Workflow
tool's user interface.
l
Anoto Pen Director 2.8 is not supported on Windows Server 2012 and Windows 10.
l
Using the PT-PT setting to perform ICR on AlphaNumeric fields may not work properly. If you
encounter the issue, use the PT-BR setting instead, or use another PlanetPess Field in your doc-
ument design.
l
Barcode scanner task may have issues reading 2-D barcodes printed/scanned with low res-
olution. Make sure the scans and the original printed output are at least 300DPI (600 or better
recommended).
l
When printing through a Windows printer driver on Windows Server 2008 or Windows Server
2008 R2, the Job Owner setting is ignored. This is caused by a documented issue in those two
Operating Systems. Microsoft has provided no reason nor workaround for the problem, therefore
PlanetPress Workflow cannot circumvent the issue.
l
Under Windows 2000, the SharePoint output task does not work with SharePoint 2010. Under
the same OS, the PlanetPress Capture ICR does not work due to the .NET 3.5 requirement.
l
The SharePoint Output task does not validate the field contents. That's Sharepoint's respons-
ibility.
Page 28