• State Verified Answer
  • Replies 16 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 3305 views
  • Users 0 members are here
Options
Related

Trados 2022 freezes in certain segments in different projects

davide fezzardi

Hello,

I have recently upgraded from Trados Studio 2019 to 2022 (Freelance) and I see a problem occurring for each project I work on (that problem didn't occur with Trados 2017 and 2019).

In certain segments, my keyboard seems unresponsive. When I move my cursor into those segments, my keyboard seems disconnected to Trados. Regardless of what key I press nothing happens. So when that happens I have to close:

- editor pane,

- re-open the file in editor pane and be careful to avoid those segments.

In order to insert content in those segments, I have to prepare my target content in another editor (e.g. Notepad) and then copy-paste it with my mouse into Trados target segment paying attention to not press any key. 

The only thing that seems to fix that problem is the removal of resources (TMs and TBs) but I need those resources (sometimes more than a dozen) and disconnecting them is not feasible.

What can I do to avoid having every time Trados 2022 freeze?

Davide
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi  

    It is interesting that you mention 

    davide fezzardi said:
    The only thing that seems to fix that problem is the removal of resources

    I suspect between the 2, TM's are most problematic.

    Where are those resources stored? File base, network, Language Cloud, via 3rd party like Dropbox?
    Have they been well maintained and updated as there has been significant changes between versions.
    These two articles should help: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0037519 and https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0034935

    Another thing to try reduce the the strain on TM's is to have lookahead enabled:

    Trados Studio options menu with 'Enable LookAhead' checked under Translation Memory settings.

    On a different route to explore, does this article have any relevance to your scenario:  https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039395

    Please keep in touch

    Lyds

    Oana Nagy | RWS Group

    _____________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:18 AM (GMT 0) on 29 Feb 2024]
  • 0 in reply to Oana Nagy

    Hi  

    thank you very much for your reply.

    My resources are file based and included in my local hard drive (with no network, cloud or 3rd party services).

    As regards "look ahead" option, it is and was not enabled.

    I am upgrading my TMs and I will see if that problem occurs again.

    Davide 
    emoji
  • 0 in reply to davide fezzardi

    Hi  ,

    as regards TM upgrading, is there a way to upgrade a batch of TMs? I mean without opening and selecting them one by one?

    Would Glossary Converter app be useful to upgrade TMs to be used in Trados 2022? 

    Davide
    emoji
  • 0 in reply to davide fezzardi

    Just for information in case other users have my same question, I have found that installing "Trados Compatibility and Migration Power Pack" from AppStore within Trados (I had problems with the same app from web AppStore) allows the upgrade of TMX files.
    emoji
  • 0 in reply to Oana Nagy

    Hi  ,

    just an update on the issue originally reported.

    Trados currently gets stuck at segment no. 19 of my current project. I get this error message:


    Error dialog box in Trados Studio displaying message: Requested value 'type' was not found, with an OK button and links to Knowledge Base and Community.

    Then I click on "OK" and keyboard inputs do not have any effect in open segments. 

    In the last few days, I have installed the last update for Trados 2022, I have enabled LookAhead and upgraded my local-file TMs linked to my translation project.

    The following is the error details I get: 

    Fullscreen sdlerror-20221219-17h59m40s.sdlerror.xml Download 
    <SDLErrorDetails time="19/12/2022 17:59:42">
  <ErrorMessage>Requested value 'type' was not found.</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.Enum.EnumResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument)
   at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
   at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryFieldXmlProcessor.GetFieldValue(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryFieldXmlProcessor.GetFieldEntity(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryTermXmlProcessor.GetTermEntity(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryIndexXmlProcessor.GetIndexEntity(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryXmlProcessor.ReadEntry(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryXmlProcessor.GetEntryEntity(String xml)
   at Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetEntry(MultiTermTermbase termbase, Int32 id)
   at Sdl.MultiTerm.Client.TerminologyProvider.MultiTermTermbase.GetEntry(Int32 id)
   at Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetEntry(Int32 id)
   at Sdl.MultiTerm.Client.TerminologySearch.TermRecognitionHit.get_Entry()
   at Sdl.TranslationStudio.Editor.Terminology.TermBaseAutoSuggestProvider.GetSuggestionData(EditingContext context)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.SuggestionDataProviders.GetSuggestionData(EditingContext context)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.SuggestionWindow.ShowSuggestionWindow(Form parent, ISideBySideDocumentEditingView view, SideBySideEditor editor, ISuggestionDataProvider suggestionDataProvider, SuggestionSite site, Char firstChar, Int32 sourceStartPosition, SuggestionMode mode, ITranslatableDocumentEditorSettings settings, Boolean requireCaseResolving, Boolean incrementTextOffset, Int32 imeBehavior)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.ShowSuggestionWindow(Form parent, ISideBySideDocumentEditingView view, SideBySideEditor editor, ISuggestionDataProvider suggestionDataProvider, SuggestionSite site, Char firstChar, Int32 sourceStartPosition, SuggestionMode mode, ITranslatableDocumentEditorSettings settings, Boolean requireCaseResolving, Boolean incrementTextOffset)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.LaunchIntellisenseWindow(Boolean keyPressed, Char lastChar, Boolean afterImeCompositionUpdate)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.ProcessDocumentContentChanged(List`1 operations, Boolean afterImeCompositionUpdate)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.Document_ContentChanged(Object sender, FrameworkDocumentContentChangedEventArgs e)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at AbstractFrameworkDocument.raise_ContentChanged(Object value0, FrameworkDocumentContentChangedEventArgs value1)
   at AbstractFrameworkDocument.OnContentChanged(Object sender, FrameworkDocumentContentChangedEventArgs args)
   at FrameworkDocumentEventSource.RaiseContentChanged(FrameworkDocumentEventSource* )
   at FrameworkDocumentEventSource.vv_AfterCompositeCommandCompleted(FrameworkDocumentEventSource* )
   at Tree.DocumentControl.vl_WindowProc(DocumentControl* , HWND__* , UInt32 , UInt32 , Int32 )
   at FrameworkDocumentControl.vl_WindowProc(FrameworkDocumentControl* , HWND__* h_wnd, UInt32 n_msg, UInt32 w_p, Int32 l_p)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Control.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WmKeyChar(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio17</ProductVersion>
    <EntryAssemblyFileVersion>17.0.5.14757</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>[---redacted---]</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>[---redacted---]</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8286760 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>


    Generated Image Alt-Text
    [edited by: Trados AI at 9:18 AM (GMT 0) on 29 Feb 2024]
  • 0 in reply to davide fezzardi

     

    Have you applied any resources from Studio 2019 in 2022? Especially have you used your user profile from S2019? This will cause problems. Also using project templates from S2019 will cause problems.

    This said, it seems to be you have several potential solutions, listed in order from the easiest to the most complicated and of course to stop after some of these resolves the problem:

    • If you used an user profile from S2019, remove it, use a default profile and adapt to your needs
    • If no profile has been used from S2019, go to File -> Setup and chose Manage user profiles to reset the current user profile
    • When a file is open in the Editor, go to View and Reset window layout
    • If all this does not help, reset Studio as described here: gateway.sdl.com/.../communityknowledge

    From my point of view using LookAhead is very contraproductive, so I have it switched off.

    BTW, which Windows version are you using? Windows 11? Have you updated to 22H2? If so, make sure you update it again with the very recent update, as this seems to solve many problems which occurred in Studio after installing 22H2.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji
  • 0 in reply to Jerzy Czopik

    Hi  

    I have indeed reused as much resources and settings as possible from my 2019 version, especially project templates, in order to avoid potential loss of settings after the upgrade.
    I will try your suggestions as soon as possible.

    I have Windows 10 Pro version 22H2. I see no pending Windows updates.
     
    emoji
  • 0 in reply to davide fezzardi

     

    In this case your user profile from S2019 might be the first problem. I would start with resetting this to default and adapting the settings again.

    As for the project templates: the crucial part here are the file types. If you want to continue using the templates, edit each one via File -> Setup -> Project templates and simply RESET all file types there. This will make sure you are using the current file types and avoid problems. From what I know the rest should work (at least it is what I did and do not have problems here).

    From what I also know, Windows 10 22H2 did not affect Studio. At least I did not read any corresponding messages, while Windows 11 22H2 did.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji
  • 0 in reply to Jerzy Czopik

       

    I have reset my user settings to default, reset editor layout, updated my project-template filetypes and finally run a "Repair" (via Control Panel) of Trados 2022 but the problem occurs again.

    Now it seems that it takes more time to occur: I managed to type for more seconds into one of the problematic segments but then I get again the error message

    Error dialog box in Trados Studio with a red cross icon displaying the message 'Requested value 'type' was not found.' with options for Knowledge Base and Community.

    The following is the details of the error message reported above:

    Fullscreen sdlerror-20221220-10h2m43s.sdlerror.xml Download 
    <SDLErrorDetails time="20/12/2022 10:02:50">
  <ErrorMessage>Requested value 'type' was not found.</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.Enum.EnumResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument)
   at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
   at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryFieldXmlProcessor.GetFieldValue(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryFieldXmlProcessor.GetFieldEntity(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryTermXmlProcessor.GetTermEntity(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryIndexXmlProcessor.GetIndexEntity(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryXmlProcessor.ReadEntry(XmlReader reader)
   at Sdl.MultiTerm.Core.XmlProcessor.EntryXmlProcessor.GetEntryEntity(String xml)
   at Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetEntry(MultiTermTermbase termbase, Int32 id)
   at Sdl.MultiTerm.Client.TerminologyProvider.MultiTermTermbase.GetEntry(Int32 id)
   at Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetEntry(Int32 id)
   at Sdl.MultiTerm.Client.TerminologySearch.TermRecognitionHit.get_Entry()
   at Sdl.TranslationStudio.Editor.Terminology.TermBaseAutoSuggestProvider.GetSuggestionData(EditingContext context)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.SuggestionDataProviders.GetSuggestionData(EditingContext context)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.SuggestionWindow.ShowSuggestionWindow(Form parent, ISideBySideDocumentEditingView view, SideBySideEditor editor, ISuggestionDataProvider suggestionDataProvider, SuggestionSite site, Char firstChar, Int32 sourceStartPosition, SuggestionMode mode, ITranslatableDocumentEditorSettings settings, Boolean requireCaseResolving, Boolean incrementTextOffset, Int32 imeBehavior)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.ShowSuggestionWindow(Form parent, ISideBySideDocumentEditingView view, SideBySideEditor editor, ISuggestionDataProvider suggestionDataProvider, SuggestionSite site, Char firstChar, Int32 sourceStartPosition, SuggestionMode mode, ITranslatableDocumentEditorSettings settings, Boolean requireCaseResolving, Boolean incrementTextOffset)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.LaunchIntellisenseWindow(Boolean keyPressed, Char lastChar, Boolean afterImeCompositionUpdate)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.ProcessDocumentContentChanged(List`1 operations, Boolean afterImeCompositionUpdate)
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.IntellisenseEditing.Document_ContentChanged(Object sender, FrameworkDocumentContentChangedEventArgs e)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at AbstractFrameworkDocument.raise_ContentChanged(Object value0, FrameworkDocumentContentChangedEventArgs value1)
   at AbstractFrameworkDocument.OnContentChanged(Object sender, FrameworkDocumentContentChangedEventArgs args)
   at FrameworkDocumentEventSource.RaiseContentChanged(FrameworkDocumentEventSource* )
   at FrameworkDocumentEventSource.vv_AfterCompositeCommandCompleted(FrameworkDocumentEventSource* )
   at Tree.DocumentControl.vl_WindowProc(DocumentControl* , HWND__* , UInt32 , UInt32 , Int32 )
   at FrameworkDocumentControl.vl_WindowProc(FrameworkDocumentControl* , HWND__* h_wnd, UInt32 n_msg, UInt32 w_p, Int32 l_p)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Control.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WmKeyChar(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio17</ProductVersion>
    <EntryAssemblyFileVersion>17.0.5.14757</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>--redacted--</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>--redacted--</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8286760 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>


    Generated Image Alt-Text
    [edited by: Trados AI at 9:19 AM (GMT 0) on 29 Feb 2024]
  • 0 in reply to davide fezzardi

     

    I'm not an expert in reading the error messages, but it seems to be connected with MultiTerm.

    Have you installed the latest version of MultiTerm too?

    For installation:

    • Install Studio first, running the installer as admin (right click, chose "run as admin")
    • Then install MultiTerm also as admin

    When done or when MT has already been installed in the latest version, open your termbase(s) in MT and reorganize these there. Remove the TBs from project settings, restart Studio and add them again. When reorganizing TBs observe their size on the HDD. Sometimes MT blows the size so that the TB ist much bigger in megabyte after the reorganization. In this case you can repair the TB using MS Access. This helps in many cases.

    If all this does not help:

    • Export all your TMs to TMX and recreate these.
    • Export all your TBs to xml, store their definitions and recreate these too.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji