Multiterm 2017. Error messsage when trying to open Term Base

Multiterm 2017. Error messsage when trying to open Term Base. "Unable to establish connection with SDL MultiTerm Server unkonwn. Check connection setting." I have unsuccessfully tried solutions  at gateway.sdl.com/.../communityknowledge , but still doesn't work. Any ideas why? TKS!

Parents
  • Hi ,

    Is MultiTerm updated? To check it, please go to MultiTerm > Help ribbon > Check for updates button.

    Does it work?

    You can try Reset Window Layout in Trados Studio.

    If it doesn't work either, and having tried resolutions 1, 2, and 3 of https://gateway.sdl.com/apex/communityknowledge?articleName=000003939, please post the error stack as mentioned here: https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/4159/how-to-get-help-quickly-in-the-sdl-community-technical-forums

  • Thank you for your reply Jose. Yes, MultiTerm is updated and it works when Im in Trados Studio, but it does not work when I go directly to MultiTerm and want to open a term base.  Here is my error stack.

    <SDLErrorDetails time="25/2/2021 15:10:47">
      <ErrorMessage>No se ha podido establecer una conexión con SDL MultiTerm Server desconocido.
    
    Compruebe su configuración de conexión</ErrorMessage>
      <Exception>
        <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
        <HelpLink />
        <Source>Sdl.Desktop.Platform.WinForms</Source>
        <HResult>-2147467261</HResult>
        <StackTrace><![CDATA[   en Sdl.Desktop.Platform.WinForms.DockingViewContentControl.SetActiveViewPart(IViewPartReference viewPartReference)
       en Sdl.Desktop.Platform.WinForms.DockingViewContentControlEx.SetActiveViewPart(IViewPartReference viewPartReference)
       en Sdl.Desktop.Platform.AbstractViewWithParts.set_ActiveViewPart(IViewPartReference value)
       en Sdl.MultiTerm.Studio.Editor.EditorView._TermbaseService_TermbaseActivated(TermbaseStatus termbase)
       en Sdl.MultiTerm.Studio.Common.Interfaces.TermbaseActivatedHandler.Invoke(TermbaseStatus termbase)
       en Sdl.MultiTerm.Studio.Editor.TermbaseService.ActivateTermbase(TermbaseStatus termbase)
       en Sdl.MultiTerm.Studio.Editor.TermbaseService.<ActivateTermbase>b__149_0(TermbaseStatus status)
       en Sdl.MultiTerm.Studio.Editor.TermbaseService.ActivateTermbase(String path)
       en Sdl.MultiTerm.Studio.Editor.Actions.TermbaseOpenAction.Execute(ITermbaseService termbaseService)]]></StackTrace>
      </Exception>
      <Environment>
        <ProductName>SDL MultiTerm</ProductName>
        <ProductVersion>MultiTerm14</ProductVersion>
        <EntryAssemblyFileVersion>14.2.8.55461</EntryAssemblyFileVersion>
        <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
        <ServicePack>NULL</ServicePack>
        <OperatingSystemLanguage>2058</OperatingSystemLanguage>
        <CodePage>1252</CodePage>
        <LoggedOnUser>DESKTOP-L9HE3HB\Usuario</LoggedOnUser>
        <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
        <ComputerName>DESKTOP-L9HE3HB</ComputerName>
        <ConnectedToNetwork>True</ConnectedToNetwork>
        <PhysicalMemory>16539104 MB</PhysicalMemory>
      </Environment>
    </SDLErrorDetails>

  • Does it happen with a particular termbase or with any?

    Is this particular termbase in your hardrive?

  • It happens with all termbases on my hardrive (I don't use a server). I never had any problems up until mid February this year. 

Reply Children