The following error is displayed under IGC component logs at D:\CW\
[processpool.igc.IGCConvertCallable] (IGCConverter-PDF-thread-14-22:) [#670209] "Imaging failed due to an unknown error. [publish_error]
The “Target/source full path length is xxx characters, greater than maximum allowed of 260, publish may fail” error/warning is displayed in the IGC Windows service’s job status logs at http://localhost:7070/log on your master appliance.
If you see above listed error messages, then you should perform the following steps.
This limitation is because IGC supports file paths with a maximum limit of 260 characters only. This issue mainly appears in a pure IPv6 setup.
Example of a file path in IPv6 environment:
fe80-0-0-0-c16f-3b24-e26a-ca13s12.ipv6-literal.net\D$\CW\V90\data\Worker1\dataStore_case_akbjpa837c_79879712\fileManager\0.14.56.1\jobRun_24__fileMgr__tmp\xe_tmp\tempFiles\d26\bce\ff831b500b4a10f95686874bb5\conv-1\image\0.7.65.5115_MixedMode_Production_Slipsheet.tif
In this example, <fe80-0-0-0-c16f-3b24-e26a-ca13s12.ipv6-literal.net> is the IPv6 machine name which results into a longer path.
Users can get this error in Caching, Bulk Redaction, Production, or Production/Metadata export workflows. A workaround to fix this issue is mentioned below.
Guidelines for setting the value of these two properties:
Ensure that the length of the file path (i.e. value of these properties) excluding the <hostname> should be less than or equal to 30 characters.
For example: in