Recurrent and apparently harmless error when preparing TTX projects with Studio 2014
Thread poster: Jacques DP

Jacques DP  Identity Verified
Switzerland
Local time: 05:13
Member (2003)
English to French
Sep 24, 2014

Hello there,

Again, I am preparing a Studio project with TTX files, and I am getting this error on certain files:

Object reference not set to an instance of an object.

Details of the error below. It is a "null reference" (programming error, with assumptions that were not verified and not tested and derailed the processing) that has to do with "QuickTags", apparently.

I have had this before (at least the message above; didn't check the details the other times), I ignored it and I don't think it created problems later. Still I'd rather sort this out if possible. I have seen other threads pointing to the same message, but it seems to pop up in a variety of circumstances, hence the details.

Type: System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: mscorlib
HResult: -2147467261
StackTrace:
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Sdl.FileTypeSupport.Filters.Ttx.QuickTags.QuickTagsFactory.GetQuickTags(String fileTypeId, String fileType, Func`1 buildQuickTags)
at Sdl.FileTypeSupport.Filters.Ttx.QuickTags.QuickTagsFactory.BuildPluginConvertedQuickTags(String fileTypeDefGuid)
at Sdl.FileTypeSupport.Filters.Ttx.QuickTags.QuickTagsFactory.GetQuickTags(IFileProperties fileProperties)
at Sdl.FileTypeSupport.Framework.Integration.FilterDefinition.GetQuickInserts(ISettingsBundle settingsBundle, IFileProperties fileProperties)
at Sdl.ProjectApi.Helpers.TranslationUtils.GetQuickTags(ISettingsBundle settingsBundle, IFileTypeManager filterManager, IFileProperties fileProperties)
at Sdl.ProjectApi.AutomaticTasks.TranslationMemoryLookupContentProcessor.get_QuickTags()
at Sdl.ProjectApi.AutomaticTasks.TranslationMemoryLookupContentProcessor.CreateTranslation(TaskSegmentSearchData segmentSearchData, SearchResult searchResult)
at Sdl.ProjectApi.AutomaticTasks.TranslationMemoryLookupContentProcessor.ResolveSearchResults(SearchResults searchResults, TaskSegmentSearchData segmentSearchData)
at Sdl.ProjectApi.AutomaticTasks.TranslationMemoryLookupContentProcessor.ProcessBuffer()
at Sdl.ProjectApi.AutomaticTasks.TranslationMemoryLookupContentProcessor.ProcessWaitingParagraphs()
at Sdl.ProjectApi.AutomaticTasks.TranslationMemoryLookupContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
at Sdl.FileTypeSupport.Filters.Processors.SegmentRenumberingBilingualProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.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.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 groupElement)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.
b__f(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.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.TaskFileExecuter.Parse(String targetFilePath


 

Jacques DP  Identity Verified
Switzerland
Local time: 05:13
Member (2003)
English to French
TOPIC STARTER
Still getting this error on some of my files Sep 29, 2014

The TTX are prepared by the clients with Trados 2007. Some TTX produce this error at the stage described above. I still don't know if it has consequences. I believe it is a programming error where some assumption is not verified (hence a "null reference").

I have found this in the KB
http://kb.sdl.com/#tab:homeTab:crumb:7:artId:4984

But though the message is the same, the symptoms don't match, so I have not applied the procedures.


 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Recurrent and apparently harmless error when preparing TTX projects with Studio 2014

Advanced search







PerfectIt consistency checker
Faster Checking, Greater Accuracy

PerfectIt helps deliver error-free documents. It improves consistency, ensures quality and helps to enforce style guides. It’s a powerful tool for pro users, and comes with the assurance of a 30-day money back guarantee.

More info »
SDL Trados Studio 2019 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running, helps experienced users make the most of the powerful features, ensures new

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search