1. General - Recent Threads

Trados 2026 can't connect with Groupshare 2020

Juan José Serrano — Thu, 13 Aug 2026 11:52:21 GMT

Hi,

We had Trados 2024 and GroupShare 2020 installed and working together seamlessly. Last month, we acquired Trados 2026 and upgraded from Trados 2024.

Now, we are unable to connect to GroupShare—neither to the translation memories nor the projects. The server returns a connection error.
We have tested both with and without HTTPS, but we cannot access or even connect to the system.

We are, however, able to access it via the web interface.

This is a major issue for us. Is there a patch available, or are there instructions on how to get everything working normally again?

Thanks!

RE: Trados 2026 can't connect with Groupshare 2020

Juan José Serrano — Fri, 14 Aug 2026 05:58:33 GMT

Yes, you are right. It was due to the update to CU15. We reverted to the previous version (GS 2020 SR1 CU12) because the installation encountered errors and was not working correctly. T

hank you for your help!

RE: Trados 2026 can't connect with Groupshare 2020

Simon Bratina — Thu, 13 Aug 2026 13:35:41 GMT

Hi Juan José Serrano

I just noticed your post about issues after the update from GS 2020 SR1 CU12 to CU15 ... Error installing SR2 on Groupshare 2020

Hence, my question above is answered and feedback may not be that relevant .... as my testing environment is on an older build.

Simon

RE: Trados 2026 can't connect with Groupshare 2020

Simon Bratina — Thu, 13 Aug 2026 12:22:24 GMT

Hi Juan José Serrano

Can you check and share the version of GroupShare 2020 server you are trying to work with?

My understanding is that older versions of GS 2020 server could have issues with authentication on it and consequently not being able to work with resources there.

Have tested the Trados 2026 being able to connect and use resources on GroupShare 2020 SR1 CU 8.1 - if GroupShare account is used for authentication.

Simon

RE: "You cannot check in the selected files because an error occurred while synchronizing the project": How can I solve this issue?

Peter Laborczi — Thu, 13 Aug 2026 05:35:28 GMT

We are facing the same issue. In some cases, the CascadeItem is duplicated at the root level of the SDLPROJ file.

When we publish the project to GroupShare and synchronize it, the SDLPROJ file is valid and contains only one CascadeItem tag.
However, when a new file is added to the project and then synchronized with GroupShare, the SDLPROJ file sometimes becomes corrupted in GroupShare, as shown below:

The issue seems to occur randomly. Sometimes everything works as expected, while in other cases the CascadeItem is duplicated.

Could you please help us investigate this issue and identify what might be causing it?

"You cannot check in the selected files because an error occurred while synchronizing the project": How can I solve this issue?

Alessia Nasini — Fri, 15 Jul 2022 09:33:44 GMT

We originally got this issue from the translator when she was trying to check the translated file in.

Then this problem extended to all the files in that project when we tried to check-in the files after Finalisation.

It also happened with a single file in a big project a few weeks ago.

In neither cases we we able to syncronize again and the project is now stucked.

I am adding the xml error.

Can anyone give a hint?

Thanks a lot,

Alessia

[View:/cfs-file/__key/communityserver-discussions-components-files/347/sdlerror_2D00_2022715_2D00_11h28m50s.sdlerror.xml:900:600]

Trados Studio 2026 asking for security code when setting up Groupshare servers although MFA is not enabled in Groupshare

Karlito — Mon, 03 Aug 2026 14:19:35 GMT

After installing Studio 2026, I cannot connect to Groupshare servers. Trados either throws a connection error or keeps asking for a security code although MFA is turned off on the server side of Groupshare.

The SSL settings are also entered correctly on Trados (443 with SSL box ticked) and the Groupshare server is accessible via a browser.

If I log in from Trados 2024, I have no issues. Then, the connection stays alive for a while and I can connect via Trados studio 2026 until the session expires.

Since I thought that the issue was caused via a clash between the two software versions, I did the following, but the problem persists with all Groupshare connections I've tried:

1. Removed Groupshare server settings and tried again - didn't help

- Created a new password on Groupshare and made sure that MFA was turned off. - didn't help.
- Turned MFA on the server side and the code is also not accepted by Trados.

- Disabled Firewalls and cleared DNS cache - didn't help

2. I removed Trados licences and uninstalled all versions of Trados studio + plugins from the disk.

- Cleared all trados/SDL folders from the Program Files, Program Files (x86), ProgramData and from Local/Roaming in the Users>AppData directory

- Ran CCleaner Reg cleaner and Bleachbit

- Restarted the PC

- Reinstalled Trados 2026

... but the problem persists.

So basically I can't use Trados 2026 because I mainly work on Groupshare projects.

What else can I do? As I mentioned earlier, everything runs fine on Trados 2024 SR1

Problem connecting to a GroupShare Termbase in Studio 2024

jean mitchell — Thu, 30 Jul 2026 10:16:44 GMT

I have been attempting to connect to a client's GroupShare termbase in Studio 2024, but can't get past the entries for the address and port. When I enter the address, the default port changes from 80 to 443 and the secure connection checkbox is ticked. If I untick this, it changes back to 80. I need to use 85 for the port, but when I type this in the figures also appear above as part of the address. The error message then asks me to check the access details. Does anyone know how to resolve this issue? Thanks in advance for any suggestions.

Error installing SR2 on Groupshare 2020

Juan José Serrano — Thu, 23 Jul 2026 10:25:57 GMT

Hi,

We have just migrated to Trados 2026, and before doing so, we want to update our GroupShare 2021 (GS 2020 SR1 CU12) to the latest version, SR2 CU15. We read the instructions:

https://gateway.rws.com/csm?id=kb_article&sysparm_article=KB0027397

and proceeded with the update. However, once the installation was complete, errors appeared::

System.Exception: ConfigureChefDeployments returned with code 1
en Sdl.Distribution.ServerInstall.Wizard.PostInstallStep.<DoConfiguration>b__3_1(Object sender, RunWorkerCompletedEventArgs args)
en System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
en System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
en System.Windows.Threading.DispatcherOperation.InvokeImpl()
en System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
en MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
en System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
en MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
en System.Windows.Threading.DispatcherOperation.Invoke()
en System.Windows.Threading.Dispatcher.ProcessQueue()
en System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
en MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
en MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
en System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
en MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
en MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
en System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
en System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
en System.Windows.Application.RunDispatcher(Object ignore)
en System.Windows.Application.RunInternal(Window window)
en System.Windows.Application.Run(Window window)
en Sdl.Enterprise2.Installers.EnterpriseEdition.Program.Main(String[] args)

We had to restore the backup files. We have checked the antivirus, and it is not interfering with the installation.

Any ideas where the problem might lie? We look on the knowledge database and see other people with the same problem:

[mention:caa29e6277f8461a95d0165d00160215:46448885d0e64133bbfbf0cd7b0fd6f7]

Thanks!

Groupshare CU10 throws and error on calling and configure chef

Jesus Duran — Fri, 09 Aug 2019 11:38:26 GMT

Hello everyone, I take some day trying to install Groupshare CU10 but calling Chef, it throws this error. I have tried to change the raptor file to everyone to have permission and on recipes of programdata the defalut file has everything well.

Who might me suggest a solution?

Thanks beforehand

System.Exception: ConfigureChefDeployments returned with code 1
   en Sdl.Distribution.ServerInstall.Wizard.PostInstallStep.<DoConfiguration>b__3_1(Object sender, RunWorkerCompletedEventArgs args)
   en System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
   en System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
   en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   en System.Windows.Threading.DispatcherOperation.InvokeImpl()
   en System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   en MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   en System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   en MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   en System.Windows.Threading.DispatcherOperation.Invoke()
   en System.Windows.Threading.Dispatcher.ProcessQueue()
   en System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   en MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   en MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   en System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   en MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   en MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   en System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   en System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   en System.Windows.Application.RunDispatcher(Object ignore)
   en System.Windows.Application.RunInternal(Window window)
   en System.Windows.Application.Run(Window window)
   en Sdl.Enterprise2.Installers.EnterpriseEdition.Program.Main(String[] args)

RE: Groupshare CU10 throws and error on calling and configure chef

Angelo Caltagirone — Thu, 16 Jul 2026 13:29:35 GMT

Hi Nick Date

I have a similar problem (I posted a question in this forum Error at the end of upgrading GroupShare 2020 to CU15 ) but I cannot find the article you linked anymore. Do you know where I can find it? Or who can help me?

Thank you, Angelo

Error at the end of upgrading GroupShare 2020 to CU15

Angelo Caltagirone — Thu, 16 Jul 2026 13:19:19 GMT

Normally CUs update work fine. This last one gets an error at the end of installation (before upgrading the termbases):

System.Exception: Database operation failed
bei Sdl.Distribution.ServerInstall.Wizard.PostInstallStep.<DoConfiguration>b__3_1(Object sender, RunWorkerCompletedEventArgs args)
bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Windows.Threading.DispatcherOperation.Invoke()
bei System.Windows.Threading.Dispatcher.ProcessQueue()
bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
bei MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
bei System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
bei System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
bei System.Windows.Application.RunDispatcher(Object ignore)
bei System.Windows.Application.RunInternal(Window window)
bei System.Windows.Application.Run(Window window)
bei Sdl.Enterprise2.Installers.EnterpriseEdition.Program.Main(String[] args)

Could somebody help? I do not have a support contract anymore, as I went over to Trados Team, but I need to use GroupShare for termbase issues, because Trados Team does not work the way I want, and with the new Studio 2026 the GS connection is very slow. This problem was solved with CU15, but I cannot upgrade it (it works on a VM that I can restore, if the upgrade does not work).

Thank you very much for any help I can get.

Regards,

Angelo

Errors in GS 2020SR2

João Ruivo — Mon, 06 Jul 2026 18:36:07 GMT

T am receiiving constantly this error:

Unable to build model! State: "{\"ModelId\":\"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\",\"InternalModelId\":99,\"ContainerId\":\"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\",\"Corpora\":\"\",\"ExceptionData\":{}}"

Is this a bug,somrting i have to be concerned what else?

i can't access the active jobs in Groupshare

Marco Huber — Tue, 30 Jun 2026 16:39:39 GMT

Hello is this a support site?

i got the message: 404 The resource you are trying to access was not found.
https://eu.cloud.trados.com/lc-api/accountusers/v1/accountusers/me

Groupshare 2020 SR1 online editor - unable to login back after logout

Šárka Králíková — Tue, 30 Jun 2026 10:51:44 GMT

When I use Groupshare Online Editor and logout from the application, I am unable for about two hours to login back. The error is as follows. There is no activity in server logs - the call does not reach the server. It looks like some problems on client side. We tried to clear cache, use a new Edge profile, use another browser (Edge, Chrome, Firefox), but the error did not change. Do you have any idea, what's wrong? Thank you very much.

Question about when installing GroupShare 2017

Jesus Duran — Thu, 04 Jun 2026 17:56:48 GMT

Hello everybody on the community, I am installing groupshare 2017 trying to upgrade windows server after windows server and I receive a rollback action when installing new services on executing sdl services console before database upsetting and installation.

could anybody of your tell me something on the respect?

Thanks before hand.

What file and what lines of the file do I have to change for the spanish language to install groupshare 2017?

Jesus Duran — Wed, 03 Jun 2026 04:52:43 GMT

Hello everybody in the community, I have a question related to groupshare 2017 which I have to install and it is in what file and what lines of the file do I have to change for the chef to respond to the spanish language?

Thanks beofore hand.

RE: Can the content of the Temp directory be safely deleted

Yuriy Belik — Fri, 29 May 2026 09:47:54 GMT

Hi Ivan,

According to KB article files older than 1 - 2 weeks can be deleted.

I would do the following:

Stop the GS services
Move the old files somewhere just incase
Start the GS services
Check server availability via web and studio.

But the best way to to log a case and get confirmation from the RWS support.

Can the content of the Temp directory be safely deleted

Ivan Peev — Wed, 27 May 2026 13:20:36 GMT

Hello,

Can the content of C:\Users\SDLTradosSrv\AppData\Local\Temp\ directory be safely deleted to free up space on the server?

Thank you!

Couldn't access GroupShare in Trados Studio and on webpage

Tian Wang — Tue, 26 May 2026 07:08:26 GMT

Hi, recently I'm having trouble connecting to GroupShare.

I tried on Trados Studio, and I got the error message asking me to check server connection and internet connection.

I checked on the Community and found some similar problems. So I tried the solutions as provided: go to the web https://logs08.sdlproducts.com.

This is what I got

I also tried another accounts (e.g. the sa and guest account), none of which worked. And I'm pretty sure the username and password are the right ones.

Can anyone help me with this please?

Thank you so much.

Tiana

We accidentally deleted a TM from server via Trados Studio interface.

Natalia Sanz Gonzalez — Wed, 29 Apr 2026 20:02:04 GMT

We accidentally deleted a TM from server using Trados Studio TM view

How can we recover it? Does it make any difference that it was deleted from Trados Studio?

RE: We accidentally deleted a TM from server via Trados Studio interface.

Yuriy Belik — Thu, 30 Apr 2026 08:11:58 GMT

Hi Natalia,

It's my personal pain in the back as users sometime delete TM.

There are two KB articles that will help you:

To avoid accidental TM deletion you can edit Power User or PM role and uncheck the Delete TM option.

GS2020 SR2 CU14: Application Service: Error: "Too many 'Viewer.CALs' allocated. Maximum is 0."

Simon Bratina — Tue, 21 Apr 2026 22:52:25 GMT

Hi,

Five years ago we opened a support ticket regarding the Application service: Error: "Too many 'Viewer.CALs' allocated. Maximum is 0."

Case Number: 00585976. At that time support kind of dismissed the ticket by suggesting this is by design.

The issue being, that we are seeing errors related to Viewer CALs in the Application Service Logs. (system configuration / Log viewer..

The problem is that there are plenty of Multiterm Editor CAL's available and in fact, none for Multiterm Viewer CAL's - as Viewer CAL's were not purchased.

I would appreciate if product development can look into this and plan the improvement to veto such "spam" messages from the Log viewer dialog and to exclude it from filling the log database in the SQL server.

Log date: Wed, Apr. 22, 2026 00:01:37 Log message: Too many 'Viewer.CALs' allocated. Maximum is 0. Exception Sdl.Enterprise2.Platform.Client.Licensing.LicenseCountExceededException: Too many 'Viewer.CALs' allocated. Maximum is 0. at Sdl.Enterprise2.Platform.Licensing.LicenseServer.CALCounter.AllocateCAL(String clientId, TimeSpan timeout) at Sdl.Enterprise2.Platform.Licensing.LicenseServer.LicenseService.CheckOut(String clientId, String featureName, TimeSpan timeout) at Sdl.Enterprise2.Platform.Client.Licensing.LicenseServiceClient.CheckOut(String clientId, String feature, TimeSpan timeout) at Sdl.Enterprise2.Platform.Licensing.Organizations.InternalLicenseClient.CheckOut(String clientId, String featureName) at Sdl.Enterprise2.Platform.Licensing.Organizations.OrganizationLicenseClient.CheckOut(String clientId, String featureName) at Sdl.Enterprise2.Platform.Licensing.ConcurrentAccessManager.TryCheckoutLicense(String clientToken, String featureName)

Thank you

SImon

Not able to log support case for Trados GroupShare

Luciano — Wed, 25 Feb 2026 15:49:45 GMT

I am not able to log a support case for Trados GroupShare even though we have a Level 2 Support and Maintenance Agreement and I am a support user on our account.

When I am forwarded to the support form I am only offered one account to chose. At our organization, we have two RWS accounts, one with SMA and the other without. I can only select the latter and thus cannot log any support tickets.

If someone from RWS reads this, I request help in solving the above issue as well as support with upgrading our Trados GroupShare installation from 2020 SR1 to 2020 SR2.

Thanks in advance.

RE: Not able to log support case for Trados GroupShare

Cristian Cozma — Tue, 24 Mar 2026 10:08:25 GMT

Dear Luciano,

We are happy to hear that a support case was eventually raised on your behalf and I hope that our team was also able to help you with the technical part of your request. If you are still encountering issues raising support cases from your RWS account, please let us know and we will do our best to address also this issues.

Best regards,