TMS - Recovery - StartIndex cannot be less than zero
000019910 |12/2/2022 1:12 PM
Scope/Environment
TMS
Symptoms/Context
In TMS 12.5, the following error can be thrown during pre-processing of an XML/dita file, sending the task to recovery: ArgumentOutOfRangeException : StartIndex cannot be less than zero.Parameter name: startIndex : Caused by ArgumentOutOfRangeException at mscorlib. StartIndex cannot be less than zero.Parameter name: startIndex : at System.String.Substring(Int32 startIndex, Int32 length) at Sdl.FileTypeSupport.Native.Xml.WhitespaceProcessor.ReleaseOutputBufferWithSpace(Boolean needToAddWhitespace) at Sdl.FileTypeSupport.Native.Xml.WhitespaceProcessor.OutputText() at Sdl.FileTypeSupport.Native.Xml.WhitespaceProcessor.InlineStartTag(IStartTagProperties tagInfo) at Sdl.FileTypeSupport.Native.Xml.LockedContentProcessor.InlineStartTag(IStartTagProperties tagInfo) at Sdl.FileTypeSupport.Framework.Core.Utilities.NativeApi.LineNumberTracker.InlineStartTag(IStartTagProperties tagInfo) at Sdl.FileTypeSupport.Native.Xml.XmlParser.RecurseNodes(XmlNodeList list) at Sdl.FileTypeSupport.Native.Xml.XmlParser.RecurseNodes(XmlNodeList list) at Sdl.FileTypeSupport.Native.Xml.XmlParser.RecurseNodes(XmlNodeList list) at Sdl.FileTypeSupport.Native.Xml.XmlParser.RecurseNodes(XmlNodeList list) at Sdl.FileTypeSupport.Native.Xml.XmlParser.RecurseNodes(XmlNodeList list) at Sdl.FileTypeSupport.Native.Xml.XmlParser.DuringParsing() at Sdl.FileTypeSupport.Framework.NativeApi.AbstractNativeFileParser.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.Extract(PreprocessingWorkItem item) at Sdl.Tms.Ppt.PptBaseCore.PreProcess(Int32 taskId, Boolean checkFormatPainting) at Sdl.Tms.Workflow.PreProcess.PreProcess.Execute() at Sdl.Tms.MessageProcessing.WorkerRequestProcessor.ExecuteMessage() |
Resolution
Check the source file. If there are any elements for which the translatable string is whitespace only, this can cause the issue. Removing the whitespace will often allow the file to process correctly. |
Root Cause
This is a known issue, fixed in TMS 12.6. |
Reference