Task submitted to Recovery with the following error message in task history: Task: 123456 failed while being retrieved from the MT Engine. The last reported error was: SDLBeGlobalV4MTProvider:Unable to retrieve the content from the MT Provider: SDLBeGlobalV4MTProvider for task: 123456. The error given was: Error getting job status: See the log file for further details. Please take the necessary action to resolve and then recover the task. The following error message can also be found in the Archiver logs in TMS MTTranslationBase.LogMessage: SDLBeGlobalV4MTProvider:Exception occurred while importing the ITD translations: Unable to update: 78. The error given was: Sequence contains no elements at Sdl.Tms.Ppt.Emt.ApplyProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.EventFiringBilingualProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.ParagraphUnitBuffer.ProcessParagraphUnit(IParagraphUnit pu) at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OutputParagraphUnit(IParagraphUnit pu) at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseLocalizableParagraphUnit(transunit transunit, LockTypeFlags lockFlags) at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseTransUnit(transunit transunit) at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseGroup(group group) at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnGroup(XmlElement group) at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.<ContinueScanning>b__14_11(ISdlXliffStreamContentHandler handler) at System.Collections.Generic.List`1.ForEach(Action`1 action) at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning() at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing() at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseNext() at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext() at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext() at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse() at Sdl.Tms.Ppt.PptBaseCore.ApplyEMTSegments(Int32 taskId, IEnumerable`1 segments, Boolean repetitionsWereTranslated, Boolean workWithTranslationUnits) at Sdl.Tms.Archiver.Emt.Apply.RetrieveMTTranslation.GetAndUpdateTranslationThroughItd() In these examples, segment 78 of Task ID 123456. These values may be different. |
Go to the segment from the error and lock the segment, search for similar segments and lock them (download bilingual file from SDL TMS, lock the segments needed in Studio, save the modifications,upload bilingual file back to TMS) and afterwards submit the task out of Recovery. Example of culprit segment: |
1. There is at least one segment with strange characters that breaks the Language Weaver translation, in this case the segment is recorded in the error message: 11 (CRQ-21495) 2. The source file included an empty segment and TMS did not remove the empty segment before sending the file to MT (CRQ-21735) |