Lucrezia Lodato 

Can you share the log /stack trace that falls part of the error?
Please also confirm if it's a specific source file or a general issue.
Do all assigned users struggle or just 1?

While this happens in the OLE, what happens if you try open it in Studio?

Please also confirm what versions of the solution you are using, as I have checked with others and while this error has been reported on before little is known about the reasons behind the error.

Any additional detail would aid us in understanding this unknown error. 

Thank you

Lyds

Hello Lydia Simplicio, thank you for your answer. 

Unfortunately, I can't share the log /stack trace that falls part of the error.

I was the only assigned user, so I can make no comparisons with others.

And I was opening it in Studio itself, checking out the project package via Groupshare, but still in Studio itself.

About my version, it is the very latest, just updated: TradosStudio2022SR2_17.2.8.18668. Maybe is an issue with this new upgrade?

I really don't know what else I could share, I'm sorry :(

Lucrezia Lodato 

Lucrezia Lodato said:

I really don't know what else I could share, I'm sorry :(

Perhaps tell us if you have any plugins installed as this may have offered a pointer to where the problem may have been coming from.  Also, a very important one would be what version of GroupShare were you working with and what version of Trados Studio did you have installed before?  Perhaps there is an incompatibility problem there?

Otherwise, without the error message, the full stack, you have not provided much to go on.

I don't have any plugins installed. I don't know how to see the GroupShare version, I just connect to the client's server from my Trados, using an API; while for Trados Studio 2022, before the update I had installed the SR1_17.1.8.17828 version (now, with the update, I have TradosStudio2022SR2_17.2.8.18668). 

I hope this helps a little bit more. Anyway, when the clients shares a new projects and I encounter this issue again, I can take a screenshot of the error message. But I hope it doesn't happen again! Do you know if anyone else has encoutered it after the latest update? Paul 

Lucrezia Lodato 

Lucrezia Lodato said:

I don't know how to see the GroupShare version

You ask your client.

Lucrezia Lodato said:

I just connect to the client's server from my Trados, using an API

What does that mean?  Have you developed a plugin, or are you using a plugin developed by others?  This comment seems to conflict with yo saying you don't use any plugins.

Anyway, there is insufficient information here to be able to help.  I'm not aware of any similar reports so it might have even been a one-off glitch.  The best thing is probably for yo to share more error details if it happens again.

Lucrezia Lodato 

Lucrezia Lodato said:

I don't know how to see the GroupShare version

You ask your client.

Lucrezia Lodato said:

I just connect to the client's server from my Trados, using an API

What does that mean?  Have you developed a plugin, or are you using a plugin developed by others?  This comment seems to conflict with yo saying you don't use any plugins.

Anyway, there is insufficient information here to be able to help.  I'm not aware of any similar reports so it might have even been a one-off glitch.  The best thing is probably for yo to share more error details if it happens again.

Ok, thank you. 

As far as I know, there are no plugins, even if I check in the plugin list. To make it clearer, I am connected to the client's server of GroupShare in this way: File > Servers > Add, with their server address and Port. It has always worked, for more than an year. The only thing I do when there is a new project, I click on the “Click here to open this GroupShare project” link in the job page in their portal. This open Trados, usually with no problems. Paul 

I got the same error on a project out of GroupShare, I can't open the file, so I can't work.

I am also on the latest version of Trados Studio 2022 SR2 - 17.2.9.18688. Windows 10.

Julien ROUWENS 

Same questions to you as before.  You need to provide more info as we don't know what version of GroupShare you work with and this could be a problem.  Also have you contacted your client and asked them to help?

The project template was pointing on TMs located on GroupShare, I asked the version to my client, this is detailed below : 

GroupShare 2022 

UI: 15.1.8
GS: 15.1.8.10979 - GS 2020 SR1 CU08

HI Julien ROUWENS Lucrezia Lodato , the error message (Value cannot be null.Parameter name: cookie) it is a generic one and the expanded stack trace should give us more details. Here you can find details on how to save the error: https://gateway.sdl.com/apex/communityknowledge?articleName=000013936 .

I will wait for the stack trace and then I can try to guide you to solve it.

Alex J.

Alex Jude  Here's a stack trace from another client experiencing this issue. The client has uninstalled and re-installed Studio, checked for updates etc. There are no specific plugins installed.

<SDLErrorDetails time="16/01/2024 07:21:00">
<ErrorMessage>Value cannot be null.
Parameter name: Value cannot be null.
Parameter name: cookie</ErrorMessage>
<Exception>
<Type>System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<ParamName>Value cannot be null.
Parameter name: cookie</ParamName>
<HelpLink />
<Source>Sdl.MultiTerm.Client.Connectors</Source>
<HResult>-2147467261</HResult>
<StackTrace><![CDATA[ at Sdl.MultiTerm.Client.Connectors.ServerConnector.GetCatalogXMLRepresentationForType(String Cookie, Int32 l_UserActingID, Int32 l_ObjectType, Boolean vb_needDescription)
at Sdl.MultiTerm.Client.TerminologyProvider.MultiTermTermbase.GetFilters()
at Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetFilters()
at Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseProvider.UpdateTermbasesContextFilters()
at Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseProvider.SetTermbases(IList`1 termbases)
at Sdl.TranslationStudio.Editor.Terminology.TermAccessProvider.RegisterDocument(ITranslatableDocument document)
at Sdl.TranslationStudio.Editor.Terminology.TermAccessProvider.editorService_DocumentOpened(IDocument document)
at Sdl.TranslationStudio.Api.Editor.DocumentEventHandler.Invoke(IDocument document)
at Sdl.TranslationStudio.Editor.EditorService.OnDocumentOpened(IDocument document)
at Sdl.TranslationStudio.Editor.EditorService.document_Loaded(IDocument document)
at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.OnLoaded()
at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.OnLoaded()
at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.AfterLoad(IJob job)]]></StackTrace>
</Exception>
<Environment>
<ProductName>Trados Studio</ProductName>
<ProductVersion>Studio17</ProductVersion>
<EntryAssemblyFileVersion>17.2.9.18688</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>2057</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>LAPTOP-JG0D7HUC\kevin</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>LAPTOP-JG0D7HUC</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>6206548 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>

HiJulien ROUWENS ,

The reported issue was logged as a defect in Trados Studio 2022 SR2 CU9 (defect ID CRQ-36543), and this fx is scheduled to be included in the next release: Trados Studio 2022 SR2 CU10.

The issue was spotted when a user is unable to work on project files when that user doesn't have access to the Termbases referenced in the project.

Also there is a second scenario when deleting or renaming a GroupShare Termbase referenced in the project.

I hope this helps.

Alex J.

Hi, I just got this error, too. It is strange, as I could open the files before. I just closed it for a couple of minutes, as I needed to work on another file. And now I am not able to open it anymore.