Hi Jerzy,

We think it’s something related to the terminology settings.  Would be useful to get the project folder (zipped) and the template (.sdltpl or .splproj) in order to diagnose and debug?  Does setting the terminology to “Keep” prevent this from happening?

Hi Paul

I will put the customer package and the template on your FTP.

Changing the settings in terminology to "keep" results in a different error:

<SDLErrorDetails time="16.09.2014 18:13:11">

 <ErrorMessage>Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index</ErrorMessage>

 <Exception>

   <Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>

   <ParamName>index</ParamName>

   <HelpLink />

   <Source>mscorlib</Source>

   <HResult>-2146233086</HResult>

   <StackTrace><![CDATA[   at System.ThrowHelper.ThrowArgumentOutOfRangeException()

  at System.Collections.Generic.List`1.get_Item(Int32 index)

  at System.Collections.ObjectModel.Collection`1.get_Item(Int32 index)

  at Sdl.TranslationStudio.Editor.Terminology.TermbaseProvider.<SetTermbases>b__c(TermbaseContext tc)

  at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)

  at Sdl.TranslationStudio.Editor.Terminology.TermbaseProvider.SetTermbases(IList`1 termbases)

  at Sdl.TranslationStudio.Editor.Terminology.TermAccessProvider.RegisterDocument(ITranslatableDocument document)

  at Sdl.TranslationStudio.Editor.Terminology.TermAccessProvider.editorService_DocumentOpened(IDocument document)

  at Sdl.TranslationStudio.Api.Editor.DocumentEventHandler.Invoke(IDocument document)

  at Sdl.TranslationStudio.Editor.EditorService.OnDocumentOpened(IDocument document)

  at Sdl.TranslationStudio.Editor.EditorService.document_Loaded(IDocument document)

  at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.OnLoaded()

  at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.OnLoaded()

  at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.AfterLoad(IJob job)]]></StackTrace>

 </Exception>

 <Environment>

   <ProductName>SDL Trados Studio</ProductName>

   <ProductVersion>11.0.0.0</ProductVersion>

   <EntryAssemblyFileVersion>11.1.4095.0</EntryAssemblyFileVersion>

   <OperatingSystem>Microsoft Windows 8.1 Pro mit Media Center</OperatingSystem>

   <ServicePack>NULL</ServicePack>

   <OperatingSystemLanguage>1031</OperatingSystemLanguage>

   <CodePage>1252</CodePage>

   <LoggedOnUser>SPITFIRE\Jerzy Czopik</LoggedOnUser>

   <DotNetFrameWork>4.0.30319.34014</DotNetFrameWork>

   <ComputerName>SPITFIRE</ComputerName>

   <ConnectedToNetwork>True</ConnectedToNetwork>

   <PhysicalMemory>16730600 MB</PhysicalMemory>

 </Environment>

</SDLErrorDetails>

Thanks Jerzy... will come back to you.

Hi Jerzy,

As yet, we've been unable to re-create the issue in our testing environment. We do know, however, that there are a couple of potential "niggles" when it comes to updating the terminology settings in the project. For now we think it's best if you repair the terminology settings on your project and leave the option for terminology as "Keep". To repair the terminology settings for the project you'll need to open the Project Settings dialog and navigate to the Termbases section. Correct the list of Termbases there and also the Languages section underneath. That should allow you to work with the project again.

We'll continue to look at the issue and if we can find a fix we'll publish a new version of the plug-in.

Regards,

David

Hi David

Indeed... The project I've send you had no termbases and with this configuration the files inside wouldn't open. Now I added a termbase and the files do open with no error.

Will check it with the next project :)

Kind regards, Jerzy

Hi again

It looks like when keeping the TB settings untouched the app would do what it should. So applying the TB settings is that tricky?

Kind regards, Jerzy

Hi Jerzy. Sorry for not replying sooner. It seems that there may be a glitch in the Studio API so I've raised an issue with the development team to have it fixed. It doesn't happen all the time but for some termbases, it appears to corrupt the configuration.

Regards,

David