Studio 2021 Translation Memory (TM) Issues

In the last couple weeks, I have been plagued with issues when trying to import/update TMs in Studio 2021. (I have noticed that if I use Studio 2019, I do not experience these issues).

Here is the most recent error message that occurs in Studio 2021 when I try to update the main TM, but does not occur in 2019.

<SDLErrorDetails time="2021/03/07 9:39:59">
  <ErrorMessage>オブジェクト参照がオブジェクト インスタンスに設定されていません。</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.ProjectApi.AutomaticTasks</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   場所 Sdl.ProjectApi.AutomaticTasks.Tasks.UpdateTm.UpdateTranslationSystemFieldsProcessor.UpdateTranslationUnitSystemFields(UpdateItem updateItem)
   場所 Sdl.ProjectApi.AutomaticTasks.UpdateTm.AbstractUpdateTmContentProcessor.ProcessBuffer()
   場所 Sdl.ProjectApi.AutomaticTasks.UpdateTm.AbstractUpdateTmContentProcessor.ProcessWaitingParagraphs()
   場所 Sdl.ProjectApi.AutomaticTasks.UpdateTm.AbstractUpdateTmContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Filters.Processors.SegmentRenumberingBilingualProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   場所 Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.ParagraphUnitBuffer.ProcessParagraphUnit(IParagraphUnit pu)
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OutputParagraphUnit(IParagraphUnit pu)
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseLocalizableParagraphUnit(transunit transunit, LockTypeFlags lockFlags)
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseTransUnit(transunit transunit)
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnTranslationUnit(XmlElement translationUnit)
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.<ContinueScanning>b__14_12(ISdlXliffStreamContentHandler handler)
   場所 System.Collections.Generic.List`1.ForEach(Action`1 action)
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing()
   場所 Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseNext()
   場所 Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   場所 Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   場所 Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   場所 Sdl.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.TaskFileExecuter.Parse(String targetFilePath)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.1.4.4184</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1041</OperatingSystemLanguage>
    <CodePage>932</CodePage>
    <LoggedOnUser>ITP\jesse_good</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-UAO59IV</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>67022748 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Also, beside the error above, I have experienced the following issues which other users have reported about Studio 2021:

https://community.sdl.com/product-groups/translationproductivity/f/studio/34424/tm-error-message-an-error-occurred-while-using-the-tm-provider-the-tm-file-data-engine-returned-database-is-locked

https://community.sdl.com/product-groups/translationproductivity/f/studio/34314/studio-2021--can-t-update-import-into-tms/112616#112616

I have also noticed a lot of freezing and data corruption with large TMs in 2021 that I did not experience in 2019.

Questions:
1. I do not experience these problems with Studio 2019. What has changed in Studio 2021?

2. Is it now required to upgrade your in 2021? I do not want to upgrade my large TMs if possible, because the size will quadruple (ex. 1GB becomes 4GB)

Currently my solution to most of these problems is to got back to 2019 when I need to work with TMs.

Parents
  • Hi

    You seem to have a string of concerns so let me first address your 2 questions.

    Q1. I do not experience these problems with Studio 2019. What has changed in Studio 2021?

    Trados Studio 2012 have a number of changes.
    They are listed in our release notes: https://docs.sdl.com/813470/788602/sdl-trados-studio-2021-sr1/custom-auto-localization-formats

    1 Specifically relates to how TM's behave with regards to the custom auto-localization formats.

    Q2. Is it now required to upgrade your in 2021? I do not want to upgrade my large TMs if possible, because the size will quadruple (ex. 1GB becomes 4GB)

    It is best practice to upgrade your translation memories each time you switch from one version of Trados Studio to another. Only this way can you make sure your TMs remain healthy, and assure optimal performance and robustness. Especially given the TM enhancements and productivity gains between Studio 2019 and Studio 2021.

    What you can try is a repair of Trados Studio 2012 to see if it resolves any of your points raised.
    But it would be unrealistic to expect a perfect solution if you dont want to maintain your TM's.

    Let me know if you feel we can support you further

    Lydia

     

    Oana Nagy | Developer Experience | QA Engineer | RWS Group

Reply
  • Hi

    You seem to have a string of concerns so let me first address your 2 questions.

    Q1. I do not experience these problems with Studio 2019. What has changed in Studio 2021?

    Trados Studio 2012 have a number of changes.
    They are listed in our release notes: https://docs.sdl.com/813470/788602/sdl-trados-studio-2021-sr1/custom-auto-localization-formats

    1 Specifically relates to how TM's behave with regards to the custom auto-localization formats.

    Q2. Is it now required to upgrade your in 2021? I do not want to upgrade my large TMs if possible, because the size will quadruple (ex. 1GB becomes 4GB)

    It is best practice to upgrade your translation memories each time you switch from one version of Trados Studio to another. Only this way can you make sure your TMs remain healthy, and assure optimal performance and robustness. Especially given the TM enhancements and productivity gains between Studio 2019 and Studio 2021.

    What you can try is a repair of Trados Studio 2012 to see if it resolves any of your points raised.
    But it would be unrealistic to expect a perfect solution if you dont want to maintain your TM's.

    Let me know if you feel we can support you further

    Lydia

     

    Oana Nagy | Developer Experience | QA Engineer | RWS Group

Children