SDL WorldServer: Autoerror at Segmentation - the file .... does not exist

A Task/File fails at the Segment Asset step with this error:

Completed Segment Asset step of task 2 in time [00:00:00] on engine [ENGINENAME:clone#1996236756:engine#2] with result Error. Execution output: Source asset /WorldServerMount/TestClient/Projects/72287_Testproject/Source-German (Germany)/Testfile_brochüre.idml does not exist 

Note: Engine name, directory and file name will vary. 

Also, if you try to download the source file from the UI, you will get an error saying that the file does not exist. However, if you check the directory in Explorer you will find that the file is there.

 

This issue is permanently fixed starting with WorldServer 11.3.3.

In previous versions, in order to fix this issue, the customer should

1- either change the tomcat's server.xml file and add URIEncoding="ISO-8859-1" as follows:
 

<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 to on.

Reference: https://tomcat.apache.org/migration-8.html#URIEncoding

Other workaround:

Rename the project or file name to avoid special characters and either submit a new project (if the error is related to the project name) or add the renamed file to the existing project as a new Task if the error is related to the file name.

Finally, cancel the Task in Autoerror.

Special characters such as Umlauts in the directory (project name) or file name might cause this error. This issue has been filed as defect CRQ-7063. Our developers found that this is not a specific WorldServer issue, but rather a Tomcat update issue. In tomcat 7 the default encoding is ISO-8859-1 and in tomcat 8 it is UTF-8 (if "strict servlet compliance" mode is off, which is the default).

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

This issue can also happen for reference files as project attributes. Refer to this article if this is relevant for you:

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