• State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 508 views
  • Users 0 members are here
Options
Related

Worldserver compatibility pack for Trados 2022

Luciano Oliveira Monteiro

Hello!

I had a similar problem with Trados 2021 some time ago but I gave up after nothing seemed to work.

Now I have almost the same problem with my Trados 2022 installation. I am able to download and install the relevant Worldserver Compatibility Pack for my Trados version, but whenever I try to to open a WSXZ file, I get an error message that mentions Multiterm. I do not understand why this happens, as I don't even have Multiterm installed.

The full error message is below:

Error dialog box in Trados Studio with a red cross symbol indicating an error. The message states 'Object reference not set to an instance of an object.' and includes a stack trace with references to Multiterm, WorldServer, and other internal components.

I have reinstalled everything and made sure that no other Trados installations are present on my machine. Yet the error persists. I have searched the community forums for a fix but I could not find anything.

I know I can rename Worldserver packages as zip files and extract everything to create a local project, but I really would rather take advantage of the convenience of simply opening them and focusing on translating rather than troubleshooting.

Do you think this could have something to do with Multiterm, or perhaps I should try installing another version of the Compatbility Pack (rather than the one that gets downloaded from within Trados Studio)?

Thanks in advance,

Luciano

Generated Image Alt-Text
[edited by: RWS Community AI at 9:42 PM (GMT 1) on 23 Jul 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello,

    I was able to deal with the problematic WSXZ file by renaming it as a ZIP archive, opening it, removing the TBX file, closing it and renaming it back. Then I was able to open it as a Worldserver package with no glitches (except for the absence of the term base that was supposed to have been included in the package).

    At this point it is clear to me that there is no problem with my WorldServer Compatibility Pack plug-in, but rather with how Trados Studio deals with term bases, as I originally suspected.

    I proceeded then to create a term base using Trados Studio, but I received the same "Object reference" error message. I installed Multiterm, and creating a term base was not possible, with a similar error message.

    After reading some forum messages, I tried everything possible to repair my installations. I uninstalled both Trados and Multiterm, deleted every SDL folder that I could find, and made sure that Windows was up-to-date, including the latest NET Framework version.

    Even after that, the same error persists when trying to create a term base from within Trados Studio or Multiterm.

    I was wondering if this could be investigated in greater detail, or if it would be better to create a new thread as this is clearly no longer related to WorldServer.

    Thanks in advance,

    Luciano
    emoji
Reply
  • 0

    Hello,

    I was able to deal with the problematic WSXZ file by renaming it as a ZIP archive, opening it, removing the TBX file, closing it and renaming it back. Then I was able to open it as a Worldserver package with no glitches (except for the absence of the term base that was supposed to have been included in the package).

    At this point it is clear to me that there is no problem with my WorldServer Compatibility Pack plug-in, but rather with how Trados Studio deals with term bases, as I originally suspected.

    I proceeded then to create a term base using Trados Studio, but I received the same "Object reference" error message. I installed Multiterm, and creating a term base was not possible, with a similar error message.

    After reading some forum messages, I tried everything possible to repair my installations. I uninstalled both Trados and Multiterm, deleted every SDL folder that I could find, and made sure that Windows was up-to-date, including the latest NET Framework version.

    Even after that, the same error persists when trying to create a term base from within Trados Studio or Multiterm.

    I was wondering if this could be investigated in greater detail, or if it would be better to create a new thread as this is clearly no longer related to WorldServer.

    Thanks in advance,

    Luciano
    emoji
Children
  • 0 in reply to Luciano Oliveira Monteiro

    By the way, here's a log message that I was able obtain. Apparently it shows what goes wrong when trying to create a term base.

    INFO [2024-07-30 12:23:01,212] Sdl.MultiTerm.Client.TerminologyProvider.TermbaseDefinitionWizard - Instantiating termbase definition COM object 89c25b32-3bb8-434d-9426-e9cf7e4be860.
INFO [2024-07-30 12:23:23,277] Sdl.MultiTerm.Client.TerminologyProvider.TermbaseDefinitionWizard - Written termbase definition to C:\Users\Laptop\AppData\Local\Temp\aw1qukh4.ynl.xdt.
INFO [2024-07-30 12:23:23,278] Sdl.MultiTerm.Client.TerminologyProvider.TermbaseDefinitionWizard - Releasing termbase definition COM object 89c25b32-3bb8-434d-9426-e9cf7e4be860, succeeded.
INFO [2024-07-30 12:23:23,281] Sdl.MultiTerm.Client.TerminologyProvider.TermbaseCreator - Instantiating MultiTerm application COM object 88643852-a285-4061-b9bd-def3c569f42a.
INFO [2024-07-30 12:23:24,704] Sdl.MultiTerm.Client.TerminologyProvider.TermbaseCreator - Releasing MultiTerm application COM object 88643852-a285-4061-b9bd-def3c569f42a, succeeded.
FATAL [2024-07-30 12:23:24,725] Sdl.Desktop.Platform.UnhandledException - Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
   at Sdl.MultiTerm.TMO.Interop.ITermbaseRepository.Connect(String UserId, String Password)
   at Sdl.MultiTerm.Client.TerminologyProvider.TermbaseCreator.CreateTermbase(TermbaseDefinitionWizard xdtWizard)
   at Sdl.MultiTerm.Client.TerminologyProvider.TermbaseCreator.CreateTermbase()
   at Sdl.MultiTerm.Client.TerminologyProvider.FileBasedMultiTermProviderWinFromsUI.Create()
   at Sdl.TranslationStudio.ProjectManagement.Terminology.ProjectTermbasesControl.CreateTerminologyProviderPlugin_OnClick(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.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)
INFO [2024-07-30 12:23:24,732] Sdl.Desktop.Platform.UnhandledException - Object reference not set to an instance of an object.#ProcessName=SDLTradosStudio#PhysicalMemorySize=333320192#VirtualMemorySize=240898048#ThreadCount=45#HandleCount=1880#GdiHandleCount=1374#UserHandleCount=622#TotalProcessorTime=00:00:21.4531250
INFO [2024-07-30 12:23:33,987] Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter - Finish#Id=04e4d91f-a82c-4703-9150-79bde3a40cac#Name=options#ProcessName=SDLTradosStudio#PhysicalMemorySize=327147520#VirtualMemorySize=223756288#ThreadCount=41#HandleCount=1681#GdiHandleCount=1372#UserHandleCount=590#TotalProcessorTime=00:00:21.6875000
    emoji