Product Lifecycle Management
Page tree
Skip to end of metadata
Go to start of metadata

Introduction

This issue affects version 5.2.6.0 / 1.1.6.0 and higher. 

Question or Problem

Scenario:

  • When exporting documents to a collaboration, the export stops after uploading the export metadata files if Windows finds reserved characters in the path.

Problem:

  • You get the error: "Error Exporting Document"

    [09:59:38.483] AWT-E         Illegal char <>> at index <n>: ...
[09:59:38.483] AWT-E         [Stack Trace]
[09:59:38.483] AWT-E         sun.nio.fs.WindowsPathParser.normalize(Unknown Source, /java.base)
[09:59:38.483] AWT-E         sun.nio.fs.WindowsPathParser.parse(Unknown Source, /java.base)
[09:59:38.483] AWT-E         sun.nio.fs.WindowsPathParser.parse(Unknown Source, /java.base)

  • Or same error: "Error Exporting Document" with different exception in log file:

    [08:38:58.085] BW1T0            org.apache.chemistry.opencmis.commons.exceptions.CmisUnauthorizedException: Unauthorized
[08:38:58.085] BW1T0            	at org.apache.chemistry.opencmis.client.bindings.spi.browser.AbstractBrowserBindingService.convertStatusCode(AbstractBrowserBindingService.java:324)
[08:38:58.085] BW1T0            	at org.apache.chemistry.opencmis.client.bindings.spi.browser.AbstractBrowserBindingService.read(AbstractBrowserBindingService.java:410)
[08:38:58.085] BW1T0            	at org.apache.chemistry.opencmis.client.bindings.spi.browser.ObjectServiceImpl.getObjectByPath(ObjectServiceImpl.java:315)

 


Caused by

You are using one of the following reserved characters in the Collaboration name:

    < (less than)
    > (greater than)
    : (colon)
    " (double quote)
    / (forward slash)
    \ (backslash)
    | (vertical bar or pipe)
    ? (question mark)
    * (asterisk)

For full list see: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions


Or Caused by other special characters like "%" in the Collaboration name.

Workaround 

Change your Collaboration name and don't use these reserved characters. 

Solution

An hardcoded workaround is planed for 5.2.7 (PLM-34356, PLM-34380).