When trying to open a WSXZ package in Trados Studio 2024, the process fails with this error:

There is an error in XML document (1, 257).



Note: the values in the error may vary.

Only some WSXZ packages fail to open. Others can open fine. The same WSXZ package that cannot be opened in Trados Studio 2024, can be opened fine in Trados Studio 2022.

The Studio error stack trace is:
 

<SDLErrorDetails time="11.09.2024 12:55:24">
  <ErrorMessage>There is an error in XML document (1, 257).</ErrorMessage>
  <Exception>
    <Type>System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>System.Xml</Source>
    <HResult>-2146233079</HResult>
    <StackTrace><![CDATA[   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at Sdl.ProjectApi.Implementation.Xml.TermbaseSettings.FromXml(String xml)
   at Sdl.ProjectApi.Implementation.ProjectTermbaseConfigurationProvider.GetTermbasesXml(IProjectTermbaseConfiguration termbaseConfiguration)
   at Sdl.ProjectApi.Implementation.ProjectTermbaseConfigurationProvider.GetTermbaseConfigurationXml(IProjectTermbaseConfiguration termbaseConfiguration)
   at Sdl.ProjectApi.Implementation.AbstractProjectConfigurationRepository.SetTermbaseConfiguration(IProjectTermbaseConfiguration termbaseConfiguration, IRelativePathManager pathManager)
   at Sdl.ProjectApi.Implementation.AbstractProjectConfiguration.set_TermbaseConfiguration(IProjectTermbaseConfiguration value)
   at Sdl.TranslationStudio.Packaging.WorldServer.Ws2RivelinConverter.ImportTermbases(IPackageProject targetPackage, String tbxFilePath, String xcsFilePath, IProject project)
   at Sdl.TranslationStudio.Packaging.WorldServer.Ws2RivelinConverter.HandleTerminology(IPackageProject targetPackage, IProject existingProject)
   at Sdl.TranslationStudio.Packaging.WorldServer.Ws2RivelinConverter.Convert(Boolean runAnalysisTask)
   at Sdl.TranslationStudio.Packaging.WorldServer.Packaging.WorldServerPackageConvertor.ConvertPackage(IConversionContext context, ExternalPackageConversionInfo externalPackageConversionInfo)
   at Sdl.TranslationStudioAutomation.IntegrationApi.Packaging.PackageConverterAdapter.ConvertPackage(PackageConversionInfo packageConversionInfo)
   at Sdl.TranslationStudio.Packaging.PackageImport.ConvertProjectPackageJobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.JobExecuter.Execute(JobData jobData)
   at Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message)
   at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
    <InnerException>
      <Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
      <LineNumber>1</LineNumber>
      <LinePosition>257</LinePosition>
      <SourceUri />
      <HelpLink />
      <Source>System.Xml</Source>
      <HResult>-2146232000</HResult>
      <StackTrace><![CDATA[   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   at System.Xml.XmlTextReaderImpl.ParseEntityName()
   at System.Xml.XmlTextReaderImpl.ParseEntityReference()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlTextReader.Read()
   at System.Xml.XmlReader.ReadString()
   at System.Xml.XmlTextReader.ReadString()
   at System.Xml.XmlReader.ReadElementString()
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderTermbaseSettings.Read2_TermbaseSettings(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderTermbaseSettings.Read3_TermbaseSettings()]]></StackTrace>
    </InnerException>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio18</ProductVersion>
    <EntryAssemblyFileVersion>18.0.0.1013</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>XXXXX</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>XXXX</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16492932 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

 

The issue is caused by a defect happening only in Trados Studio 2024. It happens only if the project associated with the WSXZ package has the character & in its name and contains Terminology Database (TBX file). The & character is then included in the path to the TD when opening the package, causing the error. 

This issue has been filed as defect CRQ-39707. This article will be updated as soon as a fixed version of  Trados Studio 2024 is been delivered.

Workaround 1: Avoid creating WorldServer projects with & in the project name. If possible, cancel the project on WorldServer and recreate it with a name without & in the project name. The exported WSXZ package will open fine in Trados Studio 2024.

Workaround 2: If re-creating the project in WorldServer (workaround #1) is not possible, to be able to open the WSXZ package, install Trados Studio 2022 and work with this version instead of Trados Studio 2024. 

Workaround 3: Remove the Terminology files from the affected WSXZ package. To do so, follow these steps:

1- Unzip the WSXZ package using 7-Zip with the “Extract to ‘xxxxx’” option. This will create a folder named after the package.



2- Open the folder. Locate and delete the terminology_data.tbx file.



3- Select all files and folders within the folder, right-click, and choose 7-Zip > Add to archive to create a ZIP file.



4- Rename the *.zip file you created to have a .wsxz extension and open it in Trados Studio 2024. The WSXZ package will now open, but you will not be able to view the Termbase terms associated with your project files.

The issue is caused by a defect happening only in Trados Studio 2024. It happens only if the project associated with the WSXZ package has & in its name. It can also happen when one or more files contain & in its name.

• The package has a termbase (and its location is created with the project name - which has the & character in the path).

• The deserialization method fails for termbase paths containing &.