Serge Llorca Lloret 

It would help if you could share the full error message and not just the Object Reference Error message as this is too generic.  This article explains how to get the full message and might help you solve it too:

https://multifarious.filkin.com/2023/02/22/when-error-messages-attack-using-chatgpt-to-make-peace-with-your-users

Hi Paul,

thanks for answering. I totally forgot it. Here the error:

<SDLErrorDetails time="17/01/2024 11:04:05">
  <ErrorMessage>Referencia a objeto no establecida como instancia de un objeto.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.TranslationStudio.Common</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   en Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControlUtils.AbstractUiStrategy.CanDeleteCascadeEntryItem(ProjectCascadeEntryItem cascadeEntryItem)
   en Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControlUtils.DefaultUiStrategy.UpdateButtons()
   en Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl.UpdateUi()
   en Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl.RefreshUiStrategy()
   en Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl.IsSelectedCellChanged(CellEventArgs e)
   en Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl._selectTranslationMemoryGrid_CellChange(Object sender, CellEventArgs e)
   en Infragistics.Win.UltraWinGrid.UltraGrid.OnCellChange(CellEventArgs e)
   en Infragistics.Win.UltraWinGrid.UltraGrid.FireEvent(GridEventIds id, EventArgs e)
   en Infragistics.Win.UltraWinGrid.UltraGridCell.CellChangeHelper(Object sender, EventArgs ev)
   en Infragistics.Win.EmbeddableEditorBase.RaiseValueChangedEvent()
   en Infragistics.Win.ToggleEditorBase.SetEditorValueInternal(Object newVal)
   en Infragistics.Win.ToggleEditorBase.SetNextState()
   en Infragistics.Win.CheckEditorCheckBoxUIElement.OnCheckStateChange()
   en Infragistics.Win.CheckBoxUIElement.OnClick()
   en Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
   en Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
   en Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
   en Infragistics.Win.UltraControlBase.OnMouseUp(MouseEventArgs e)
   en System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   en System.Windows.Forms.Control.WndProc(Message& m)
   en System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   en System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.8.3007</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>3082</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>YO\yo</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>YO</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>4193844 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Serge Llorca Lloret 

Thank you.  The problem could be due to a corrupt translation memory entry, a problem with the UI components not being properly initialised, or an issue where the application expects a certain object to be present, but it's not.

Since this is related to working with GroupShare projects some steps and considerations to troubleshoot and potentially resolve this issue could be:

1. GroupShare Connection: Ensure that your connection to GroupShare is stable and functioning correctly.  Problems with the network or the GroupShare server can lead to issues in loading resources like TMs or termbases.

2. Access Rights: Verify that you have the correct permissions to access and modify the TM and terminological databases in GroupShare.  Insufficient permissions can lead to errors when the software tries to access these resources.

3. Resource Integrity: There might be issues with the integrity of the TM or termbase.  If possible, try to open these resources independently or use them in a different project to see if the issue persists.  If it does, the problem might be with the resource itself rather than the project or the connection.

4. Compatibility: Make sure that the version of Studio you are using, 2019, is compatible with the version of GroupShare that your customer has.

Have you discussed this with your customer at all?  They may be able to help... they could tell you what version of GroupShare they have, what updates they might have applied in the last few months; check your permissions etc.

Thank you. Yes I have already spoken to the customer but we don't really discuss about the versions we use or what update they have done lately. I think I'll ask them and see if I can fix the problem because it's taking so long.

Also, something strange is happening and that is that despite the error, I can consult the TM and the segments that I accept are loaded to the TM (I can also see what is accepted by other translators). What does not work at all is the terminological database, it does not load.

Thanks for helping.

Hello again,

I have spoken to the customer and the version they have of Groupshare is 2020.

According to this link

gateway.sdl.com/.../communityknowledge

the trados 2019 version (the one I have) appears orange in terms of compatibility (this means according to the link: "can connect, but it is not supported/tested").

I don't quite understand the description but it could have a relation with the fact that I can't load the client TB anymore? I guess yes, but I want to be sure before upgrading. The TM works perfectly, despite the error it gives. The problem is only related to the TB.

And another thing: Does this mean that I should upgrade my trados studio to version 2022?

Thanks in advance.

Regards,
Serge