1. Home
  2. Support
Article - CS303628

Creo View Adapters: UTF-8 support for publishing CAD data with multi-byte filename and attribute characters

Modified: 21-Jan-2026   


Applies To

  • Creo Parametric 4.0 M010 to 6.0
  • Creo View Adapters 6.0 to 10.1
  • Windchill PDMLink 11.0 to 13.1
  • Windchill Visualization Services
  • Windchill Workgroup Manager
  • SolidWorks 2017, 2018, 2019, 2023
  • Siemens NX 10, 11, 12

Description

  • Are Unicode characters supported while publishing ?
  • Creo View Adapters 6.0, in conjunction with Windchill 11.2, has been enhanced with UTF-8 encoding to support the publishing of Creo Parametric, SolidWorks and Siemens NX data with multi-byte filename and attribute characters
  • Prior to Windchill 11.2 and Creo View Adapters 6.0, CAD Documents with multi-byte character filenames would fail to publish using a File Sync enabled worker, with the following error in the WVS Job Monitor:
Returned file does not exist
  • SolidWorks publish fails when CAD file name includes special characters such as φ Φ
  • In these earlier releases the CAD Worker system locale language could be set to match the filename characters following the guidance in CS298858, with the limitation being the worker was only able to support multi-byte characters of the single system locale
  • For example, attempting to publish CAD data with a filename containing Japanese characters would fail if the worker system locale language was set to Chinese
  • Using Creo View Adapters 6.0 with Windchill 11.1 M020 or earlier versions will also fail with the Returned file does not exist error
  • Solidworks worker will fail to start with error: No worker can be started, removing request from queue
  • Solidworks document publish fails when file name include Chinese Character, while the one with English file name can be successfully published
  • Fails to publish the Inventor drawing after it is checked in to Windchill
  • Backgroundmethodserver log reports 
    • ProcessMessages] wt.wvs.workeragent.ProcessMessages - message last1 : $MSG$ file.encoding=UTF-8
      java.lang.NullPointerException at com.ptc.wvs.server.cadagent.Pro      cessMessages.getMessage(ProcessMessages.java:532)
This is a printer-friendly version of Article 303628 and may be out of date. For the latest version click CS303628