Salesforce

Reference files with special characters cannot be viewed in WorldServer - Error 'Cannot find file attrxxxx....'

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer 10.4.x, 11.x
Symptoms/Context
A reference file with special characters in the file name cannot be viewed or downloaded. An internal error appears:

Cannot find file attr986969499testnameumlautüäetc.xlsx

Note: file name will vary.

The special character is not displayed correctly. This is a screenshot of how the error appears:

User-added image
Resolution

The issue is fixed permanently in WorldServer 11.3.3.

There are 2 workarounds for earlier versions:

1- change tomcat's server.xml file. Add URIEncoding="ISO-8859-1" as follows (make sure you restart WorldServer after this change):
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443"

URIEncoding="ISO-8859-1"/>
  If you are using the SSL protocol, make sure to add it to the corresponding connector as well, where the port can be either 443 or the default tomcat 8443. Here is an example:
<Connector 
protocol="org.apache.coyote.http11.Http11NioProtocol" 
port="443" maxThreads="200" 
URIEncoding="ISO-8859-1" 
scheme="https" secure="true" SSLEnabled="true" 
keystoreFile="C:\keystore\ssl-sdl-test-2018-2019.pfx" keystorePass="nopasswd" 
clientAuth="false" sslProtocol="TLS"/>
 
    2- or set the strict servlet complicance property. See reference page on the Tomcat Apache page.

    The server.xml file can be found on the server where WorldServer is installed and under this directory:

    <WS_Home>\ tomcat\conf\ server.xml 

    Alternatively, the workaround is to rename the project or file name to avoid special characters. 
     
    Root Cause
    Special characters such as Umlauts in the directory (project name) or file name might cause this error. This issue is related to several defects created around different manifestation of the issue:

    CRQ-8029
    CRQ-9193
    CRQ-6796
    CRQ-11291
    CRQ-7063
    SRQ-9609
    Reference
    Attachment 1 
    Attachment 2 
    Attachment 3 
    Attachment 4 
    Attachment 5 

    Powered by