Catalin-Ionut Pop

Trados was very slow and you did a remote test (case # 00598833). It seem to work at first, but it's back to being sluggish. For some reason, it's still very slow to open when I first click on the Trados icon in the morning. Then when I choose a document to work on, in the "Translation Memory and Document Settings" window, it stalls for quite a few minutes and it displays "Not responding" at the top of the window. Then when it does open, I usually get 2 error messages saying the same thing: "An error has occured while using the translation provider (name of my personal translation memory). The date file engine translation memory returned an error: database is locked." But it still uses the database...!!?

Also, when I "pre-translate" a file, and reopen it, it still sits at every segment and searches for a translation as if it didn't recognize that the segments are already translated! It's very time-consuming!

Then as the day goes on, it usually speeds up (maybe it's getting a coffee or something!!) :-) but usually not as fast as it used to be.

It's very frustrating when I have a big urgent document first thing in the morning and Trados just sits there, not moving...

When I go in C:/Users/Danielle/Appdata/Roaming/Trados, all the other Trados versions are still there in a folder named "Trados Studio", and there is another folder named "Trados Studio A". I thought that whenever I upgraded, it was supposed to delete the older versions. Could it be a reason why it's so slow? I don't dare delete anything without being sure. Thank you.

Hello Danielle Hart ,

When you upgrade to a new version- this isn't actually an upgrade (in software terms) from the old version- but a complete new instal.

If for instance you have upgraded from 2017 to 2021 and are no longer working (or need 2017) you can safely delete the older (2017) version (via Windows Control Panel).

However if you machine/Studio is running slowly, then it might be advisable to look at your PC (and what resources you have available)

https://www.trados.com/products/trados-studio/system-requirements.html

Also ensuring you have everything up to date can help a lot-

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/5126/01-1-windows7-and-trados-studio-multiterm-support

community.sdl.com/.../01-2-trouble-shooting-unexplained-errors-and-unwanted-behaviour-in-trados-studio-multiterm

I had already checked all those things and I have all the requirements and things are up to date. Trados litterally takes 5 minutes or more just to open a document, then it just sits on each segment for minutes at a time before offering a translation and if I use pre-translate, that takes again 4-5 minutes to run and once it's done and I reopen the file, it will stop at each segment and search for a translation when it has already filled the segment before! It's counter-intuitive and very counter-productive!  And now I have a new problem, Trados simply shuts down in a middle of my work and displays this message: "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. Cannot access a disposed object". I click Continue and it displays "An item with the same key has already been added" and I have to start over.

I had already checked all those things and I have all the requirements and things are up to date. Trados litterally takes 5 minutes or more just to open a document, then it just sits on each segment for minutes at a time before offering a translation and if I use pre-translate, that takes again 4-5 minutes to run and once it's done and I reopen the file, it will stop at each segment and search for a translation when it has already filled the segment before! It's counter-intuitive and very counter-productive!  And now I have a new problem, Trados simply shuts down in a middle of my work and displays this message: "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. Cannot access a disposed object". I click Continue and it displays "An item with the same key has already been added" and I have to start over.

Ho Danielle Hart ,

It would be really useful to see the full error stacks

Also it would be useful to know if you have the projects locally (or in the cloud) and are trying to sync with cloud storage such as OneDrive/DropBox etc or are sharing resources.

Since it is an intermittent problem, next time I get it I will copy the error stack. As for the cloud, I don't use it, everything is saved to my computer. Also, my antivirus Exploit Protection has been turned off. Thank you.

I have the xml file for the unhandled exception

<SDLErrorDetails time="2021-05-27 14:48:37">
  <ErrorMessage>An item with the same key has already been added.</ErrorMessage>
  <Exception>
    <Type>System.ArgumentException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName />
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2147024809</HResult>
    <StackTrace><![CDATA[   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at Sdl.FileTypeSupport.Framework.Native.AbstractMetaDataContainer.ReplaceMetaDataWithCloneOf(IEnumerable`1 toClone)
   at Sdl.FileTypeSupport.Framework.Native.AbstractMetaDataContainer..ctor(AbstractMetaDataContainer other)
   at Sdl.FileTypeSupport.Framework.Native.TranslationOrigin.Clone()
   at Sdl.FileTypeSupport.Framework.Native.SegmentPairProperties..ctor(SegmentPairProperties other)
   at Sdl.FileTypeSupport.Framework.Native.SegmentPairProperties.Clone()
   at Sdl.TranslationStudioAutomation.IntegrationApi.Internal.Adaptors.ApiSegmentPair.get_Properties()
   at Sdl.TranslationStudioAutomation.IntegrationApi.Internal.Adaptors.ApiSegmentPair.get_Source()
   at Sdl.TranslationStudio.Plugins.AdvancedDisplayFilter.Helpers.ColorPickerHelper.GetColors(ISegmentPair segmentPair, ContentLocation foundIn)
   at Sdl.TranslationStudio.Plugins.AdvancedDisplayFilter.Controls.DisplayFilterControl.AddNewColorCodes(ISegmentPair segmentPair)
   at Sdl.TranslationStudio.Plugins.AdvancedDisplayFilter.Controls.DisplayFilterControl.ActiveDocument_ActiveSegmentChanged(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at Sdl.Desktop.Platform.Extensions.EventsExtensions.Raise(EventHandler e, Object sender)
   at Sdl.TranslationStudioAutomation.IntegrationApi.Document.OnActiveSegmentChanged(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.OnActiveSegmentChanged()
   at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.SideBySideEditor_ActiveRowChanged(Object sender, ActiveRowChangedEventArgs e)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at SideBySideEditor.raise_ActiveRowChanged(Object value0, ActiveRowChangedEventArgs value1)
   at SideBySideEditor.OnActiveRowChanged(Object sender, ActiveRowChangedEventArgs args)
   at SideBySideEditor.set_ActiveRowNumber(Int32 rowNumber)
   at SideBySideEditor.UpdateActiveRow(IEditControl editControl)
   at SideBySideEditor.OnSelectionChanged(Object sender, SelectionChangedEventArgs args)
   at SideBySideEditor.Target_SelectionChanged(Object sender, SelectionChangedEventArgs args)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at AbstractFrameworkEditControl.raise_SelectionChanged(Object value0, SelectionChangedEventArgs value1)
   at FrameworkEditControl.OnSelectionChanged(Object sender, SelectionChangedEventArgs args)
   at FrameworkEditControlEventSource.SelectionChanged(FrameworkEditControlEventSource* )
   at Tree.InputManager.v_MoveSelection(InputManager* , TextRange* )
   at FrameworkSelection.MoveTo(Position destination, Boolean extendSelection)
   at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.MoveToStartOfTargetSegment(ISegmentContainerNode targetSegmentContainerNode, Boolean autoScroll)
   at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.MoveToNextSegment(IsValidNextSegment segmentValidator)
   at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.MoveToNextSegment(Nullable`1 segmentNavigationFilter)
   at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.ConfirmSegment(Nullable`1 segmentNavigationFilter)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.ExecuteActiveSegment()
   at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.Execute()
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
   at Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
   at Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnPreviewKeyDown(Keys keys)
   at Sdl.Desktop.Platform.WinForms.GlobalKeysMessageFilter.PreFilterMessage(Message& m)
   at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
   at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.1.6.4276</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1036</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>PcDanielle\Danielle</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>PCDANIELLE</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8171196 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

 Hi. I send you the message below one month ago with the error stack and I haven't heard back from you... Trados is still excrutiatingly slow and it more often now shuts down without warning. I'm trying to attach the error stack file on here, but it keeps asking me for a URL. So here's the stack copied and pasted. I would really appreciate some help with this problem... It is getting to the point where Trados is almost unusable... 

<?xml version="1.0"?>

-<SDLErrorDetails time="2021-06-15 14:03:06">

<ErrorMessage>Could not load file or assembly 'Aspose.Slides, Version=20.10.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)</ErrorMessage>

-<Exception>

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

<FileName>Aspose.Slides, Version=20.10.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56</FileName>

<FusionLog>WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. </FusionLog>

<HelpLink/>

<Source>Sdl.FileTypeSupport.Filters.Ppt</Source>

<HResult>-2146234304</HResult>

-<StackTrace>

-<![CDATA[ at Sdl.FileTypeSupport.Filters.Ppt.AsposeLicenser.LoadLicense()
at Sdl.FileTypeSupport.Filters.Ppt.PptSniffer..ctor(INativeFileSniffer pptxSniffer)
at Sdl.FileTypeSupport.Filters.Ppt.PptFilterComponentBuilder.BuildFileSniffer(String name)
at Sdl.FileTypeSupport.Framework.Integration.FilterDefinition.SniffFile(String nativeFilePath, Language language, Codepage suggestedCodepage, INativeTextLocationMessageReporter messageReporter, ISettingsBundle settingsBundle)
at Sdl.FileTypeSupport.Framework.Integration.FilterManager.GetAllMatchingFileTypeDefinitions(String nativeFilePath, Language suggestedSourceLanguage, Codepage suggestedCodepage, EventHandler`1 messageHandler)
at Sdl.FileTypeSupport.Framework.Integration.FilterManager.GetAllMatchingFileTypeDefinitions(String nativeFilePath, EventHandler`1 messageHandler)
at Sdl.TranslationStudio.Editor.TranslationEditor.FileScanner.SimpleScan()]]>
</StackTrace>

</Exception>

-<Environment>

<ProductName>SDL Trados Studio</ProductName>

<ProductVersion>Studio16</ProductVersion>

<EntryAssemblyFileVersion>16.1.6.4276</EntryAssemblyFileVersion>

<OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>

<ServicePack>NULL</ServicePack>

<OperatingSystemLanguage>1036</OperatingSystemLanguage>

<CodePage>1252</CodePage>

<LoggedOnUser>PcDanielle\Danielle</LoggedOnUser>

<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>

<ComputerName>PCDANIELLE</ComputerName>

<ConnectedToNetwork>True</ConnectedToNetwork>

<PhysicalMemory>8171196 MB</PhysicalMemory>

</Environment>

</SDLErrorDetails>