During the import of files in the Project wizard we encounter an error an any file type (using Trados Defaults as well as custom filters) when the process attempts the pretranslation. We can import files without error IF we do not specify any leverage. So definitely is broken the moment the leverage processs begins. Any other step thereafter equally fails.
By the next day I do not think the problem is on our end. it must be something that has changed in SR1. I run a project that was successfully executed in Trados 2019 and I see the same error type using default Trados XLIFF filter to parse the files. Something does not work with the leverage engine.
Here is an excerpt from the error log:
<ErrorMessage>Exception of type LanguagePlatformException occurred: Object reference not set to an instance of an object.
Stacktrace:
at Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemoryLanguageDirection.SearchTranslationUnitsMasked(SearchSettings settings, SubsegmentSearchSettings subsegmentSettings, SubsegmentSearchCondition condition, TranslationUnit[] translationUnits, Boolean[] mask)
at Sdl.LanguagePlatform.TranslationMemoryApi.Cascade`1.SearchSegmentAndSubSegmentTranslationUnitsMaskedCommand.Execute(T cascadeEntry, SearchSettings searchSettings)
at Sdl.LanguagePlatform.TranslationMemoryApi.Cascade`1.ExecuteSearchCommand(SearchCommand`1 searchCommand, SearchSettings searchSettings, Int32 searchResultsCount, IEnumerable`1& cascadeMessages)</ErrorMessage>
<Exception>
<Type>Sdl.ProjectApi.ProjectApiException, Sdl.ProjectApi, Version=17.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
<HelpLink />
Where do I take this problem? Thank you.
Thanks Paul!
in the meantime our internal testing revealed that the problem appears to resolve if you re-index via Update of SDLTM file in the Translation Memories panel or if you create a new SDLTM file based on the older one (requiring a 2 step process of SDLTM file creation and TMX Export/Import).
Hi Michael Metzger , Paul
we had exactly the same issue, but updating Studio to 2022 SR1 CU7 (build 17.1.7.17560) solved our problems when creating projects leveraging file-based TMs.
Hi Michael Metzger , Paul
we had exactly the same issue, but updating Studio to 2022 SR1 CU7 (build 17.1.7.17560) solved our problems when creating projects leveraging file-based TMs.
Translate
