Hello Chantal Keable Keene,

It would be great if you could tell us when you actually get this message and perhaps post the actual error stack.

.

The more information you can provide, the easier it is for us to try and help you.

Repairing/Resetting resolves many issues so perhaps you can also try the following-

gateway.sdl.com/.../communityknowledge

I did not think that I would get the error again so quickly, but I just did. Here is the stack. I am not sure if that is what you were looking for. If not, let me know how else I can post the error stack

<SDLErrorDetails time="3/23/2021 10:53:32 AM">
  <ErrorMessage>Parameter is not valid.</ErrorMessage>
  <Exception>
    <Type>System.ArgumentException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName />
    <HelpLink />
    <Source>System.Drawing</Source>
    <HResult>-2147024809</HResult>
    <StackTrace><![CDATA[   at System.Drawing.Font.GetHeight(Graphics graphics)
   at System.Drawing.Font.GetHeight()
   at System.Drawing.Font.get_Height()
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.AbstractSuggestionWindow.SetLocation()
   at Sdl.TranslationStudio.Editor.TranslationEditor.Intellisense.SuggestionWindow..ctor(ISuggestionDataProvider suggestionDataProvider, List`1 suggestionData, Form parentForm, SideBySideEditor editor, SuggestionSite site, Boolean isInternal, SuggestionMode mode, ITranslatableDocumentEditorSettings settings, Int32 imeBehavior)
   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>SDL Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.1.3.4096</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>LAPTOP-D6ONU4CR\Chant</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>LAPTOP-D6ONU4CR</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>12465380 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Hello Chantal Keable Keene ,

Perfect- this is exactly what we need :-)

When the error stack is attached like this, it makes it very easy to read.

Please try Resetting Windows Layout (easiest and quickest option)

If this fails, then please update the OS and especially the Graphics Drivers as explained here

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3392/01-2-trouble-shooting-unexplained-errors-and-unwanted-behaviour-in-trados-studio-multiterm (parts1 &2)

community.sdl.com/.../112966

Thank you. I will try resetting the windows layout tonight once I am done with my work. I am guessing that I can find the instructions for that somewhere on the web?

If that fails, I will try the other option. Keeping my fingers crossed... And I will keep you posted tomorrow, hopefully with good news.

Hello Chantal Keable Keene

Its really simple-

Thanks, it was very easy and way too good to be true. It did not work. I am still getting the error message while translating, and I have 6,000 words due tomorrow. This is a real problem right now, and slowing me down tremendously. There are some segments that I cannot translate because of that error.

Updating the OS (which I did last week) and the graphics drivers will take a while I suspect, so I will have to try that tonight during off hours.

I have not been able to work on this at all. As a matter of fact, I had to go back to using Trados 2017 the problem was so bad in 2021. The error kept popping up after every letter I typed. Insanity.

I will try the other solutions this weekend and hope that one of them works. Otherwise, I will just keep using my 2017 version that works just fine. I really think it should not be this hard to get the product that I paid for to work properly. I am so disappointed and very frustrated in having to spend all this time on this.

Hi,

I apologize for how frustrating this is.

I have opened an internal ticket for a development team to look at this and I am adding all the information that I can find.

Sometimes fixing an issue is like being a detective we just need more clues until someone has a Sherlock moment and realizes what the cause is. When we get an complaint of an issue that we are not seeing in any of our tests and users themselves are not seeing regularly it can be really difficult to get to the bottom of it.

The stack trace indicates that intellisense (the system that responds to what you type) is trying to show the suggestions window. During this operation it is trying to work out how to draw the window and contents and is measuring the height of the font it is using. Nothing particularity strange so far, but then it is throwing an error about a bad parameter which is sadly a quite generic error. 

It looks like you are using English US windows 10 Home. Do you have any particular language packs installed for windows that may have installed any fonts?

Have you changed any of the display fonts in in Studio settings?

What display language is Studio using - .i.e is the user interface of studio also in English?

What language pair were you using in the project that was having problems?

When you switched back to studio 2017 to finish the job, was that on the same PC? As it seems like you could work in 2017 if it was the same machine it may not be down to the fonts installed on the machine.

Could it be some sort of memory corruption, did you try saving and rebooting and trying again?

If you can answer these questions or give us any other information about this problem please do.

Apologies again and thanks.

I really appreciate the follow up. I will try to answer all your questions in the hopes that this will help other linguists.

I am using the US English windows 10 Home version and I did not install any language pack.

The display language in Studio is also English.

Yes, I have changed the size of the font in Studio because sometimes, it is very small and having a font size of at least 12 makes it easier to read and work on. I will try reducing the size of the font and see what happens. Unfortunately, I have not had any Studio projects this week. And since the error does not pop up all the time, it could be a week or two until it comes up again. It's a bit like a car that is making a noise and does not make it when you bring it to your mechanic.

I translate into French, and that is the language that I was using every time the error came up.

Studio 2017 is installed on the same PC. I do not have that error with the2017 version, but had it with 2019 and 2021. I also work for SDL in Montreal, and some of the technicians in that office tried to help me last fall with the 2019 version, but nothing worked. I thanked them and said that I would be installing 2021 soon, and that should resolve the issue. But no, I got the same issue with 2021.

As for the saving and rebooting, I have done that more times than I care to remember. That is always the no. 1 solution offered with all Windows issues. Shut down and reboot. So, I did that numerous times and made sure all the updates (Windows and Studio) are installed. I also corrected/repaired Studio.

I do not think it is some sort of memory corruption because this error came up with numerous clients, not just one.

I guess the only thing that we have shed light on is possibly the font. I will definitely reduce it and see what happens. However, I have always changed the font size, colors, etc. when first setting up any new version of Studio (including 2017), so it would be odd that those changes are creating a problem in 2019 and 2021, but not in 2017.

Chantal