Hello Maren Pärn ,

I haven't seen such errors associated with MS Word Spell checker before, The first error seems to suggest a problem with validating the file.

Could you please post the full error stacks  as these provide essential information to help us understand the problem.

<SDLErrorDetails time="12.02.2021 11:18:51">
<ErrorMessage>Exception has been thrown by the target of an invocation.</ErrorMessage>
<Exception>
<Type>System.Reflection.TargetInvocationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<HelpLink />
<Source>mscorlib</Source>
<HResult>-2146232828</HResult>
<StackTrace><![CDATA[ at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Sdl.SpellChecking.MSWord.OleObject.GetProperty(String propertyName)
at Sdl.SpellChecking.MSWord.MSWordSpellCheckerWrapper.GetDocument()
at Sdl.SpellChecking.MSWord.MSWordSpellCheckerWrapper.CheckSentenceIsValid(String sentence, String isoCode)
at Sdl.SpellChecking.MSWord.CachedMSWordSpellChecker.CheckSentenceIsValid(String sentence)
at Sdl.TranslationStudio.Editor.SpellChecker.GetSpellingErrorsLogic.Execute(ISegmentContainerNode segmentToCheck)
at Sdl.TranslationStudio.Editor.SpellChecker.SpellCheckToNextErrorSegmentLogic.Execute(Boolean recheckCurrentSegment)
at Sdl.TranslationStudio.Editor.SpellChecker.SpellCheckToNextErrorRangeLogic.Execute(Boolean recheckCurrentSegment)
at Sdl.TranslationStudio.Editor.SpellChecker.SpellCheckerDialogOutlookStyle.GoToNextError(Boolean recheckCurrentSegment, RangeInSegment after)
at Sdl.TranslationStudio.Editor.SpellChecker.SpellCheckerDialogOutlookStyle._btnAdd_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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>
<InnerException>
<Type>System.Runtime.InteropServices.COMException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<ErrorCode>-2147023174</ErrorCode>
<HelpLink />
<Source />
<HResult>-2147023174</HResult>
<StackTrace><![CDATA[]]></StackTrace>
</InnerException>
</Exception>
<Environment>
<ProductName>SDL Trados Studio</ProductName>
<ProductVersion>Studio16</ProductVersion>
<EntryAssemblyFileVersion>16.1.3.4096</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1033</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>MARENATWORK2\maren</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>MARENATWORK2</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>8239316 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>

Maren Pärn Support Case Id : 00581533. Support case has been logged for your assistance. Please check your SDL Community email address for updates.

As far as I know, the incompatibility between the MS Word spell checker and Trados Studio 2021 is generalized for people using Office 365.

A workaround is to use the Hunspell checker imbedded in Trados, but it is much less effective. I sure hope the incompatibility with Office 365 will ultimately be resolved.

Hello,

I have the same problem. I have Office 365 installed in my machine and MS Word Spell Checker doesn't work with Trados Studio 2021. In my native language using Hunspell doesn't help me at all.

Is it something that we can fix it, or does any member of RWS team can help me on this? Many thanks for all your help!

Best regards,

Sandra Flor

This annoying issue has been around for some time now, but it has worsened. I do hope it gets fixed. Hunspell is a very limited checker in terms of the dictionary. Too many false wrongs.