Hi Henrik , the reason why the red "X" is shown is because the connection is not established. Can you select the Cloud-based terminology (default) -> Remove. After the terminology is removed please re-establish the connection Use -> Cloud-based Terminology.

I hope this helps.

Alex J.

Thank you for the reply.

I am able to remove it, but then literally nothing happens when I try to re-establish it through Use -> Cloud-based Terminology.

Otherwise, the Cloud-Studio connection with the TMs etc. works as expected.

Hi Henrik - is there anything in the Studio log files - you can access it via "File - > View Log File" when it does not work/nothing happens, sometimes the log file will be able to tell us more. Thanks, Daniel

Hi, and thanks for the tip.

I'm not familiar with the syntax, but I guess this looks like a termbase-related problem in the Log File. Can you make anything out of it?

INFO [2023-09-20 10:22:02,427] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - begin async initializing for document text1.docx.sdlxliff
INFO [2023-09-20 10:22:02,427] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - Begin the termbases initalization. The number of calls to the server = 0
INFO [2023-09-20 10:22:02,449] Sdl.LanguageCloud.TerminologyProvider.LanguageCloudTerminologyProviderFactory - Cloud-Based Terminology Provider started
INFO [2023-09-20 10:22:02,459] Sdl.LanguageCloud.TerminologyProvider.LanguageCloudTerminologyProviderFactory - User john.doe@johndoe.com logged in to Cloud-Based Terminology Provider
ERROR [2023-09-20 10:22:02,465] Sdl.LanguageCloud.TerminologyProvider.LanguageCloudTerminologyProviderFactory - Error during initialization
System.ArgumentNullException: Value cannot be null.
Parameter name: collection
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at Sdl.LanguageCloud.TerminologyProvider.Service.PersistenceService.GetProviderSettingsList()
at Sdl.LanguageCloud.TerminologyProvider.Service.PersistenceService.Load(String user)
at Sdl.LanguageCloud.TerminologyProvider.LanguageCloudTerminologyProviderFactory.CreateTerminologyProvider(Uri terminologyProviderUri, ITerminologyProviderCredentialStore credentials)
INFO [2023-09-20 10:22:02,468] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - Initalize termbases end. The number of calls to the server = 0
INFO [2023-09-20 10:22:02,468] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - GetTermbases, initialization event fired for text1.docx.sdlxliff
INFO [2023-09-20 10:22:02,468] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - GetTermbases end initialization for text1.docx.sdlxliff

Thanks Henrik - yes, this is valuable, even if personally I don't know how to troubleshoot, but I am copying Alex Jude  and also Radu Boloveschi  here to see if they can help with this based on the log file info. It seems as if the cloud termbase settings cannot be read successfully and then an error occurs. Thanks, Daniel

Henrik We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : 00817486 .

Thank you. One more problem (sorry!), my email address has recently changed and the one I'm using here doesn't seem to forward to the new one anymore. How can I change the email?

Henrik We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : 00817684 .

Hi Henrik  I am curious, is the issue resolved now? I am experiencing the same problem for several months now. Updated from Studio 2021 to 2022 recently and hoped that it would be resolved, but unfortunately, this is not the case.

I wish I could help you. I think my problem got solved, when I had Trados re-installed due to my laptop being sent in for repair (and thus wiped).