Hello,

I'm sorry to hear that you're having trouble with the Language Weaver Provider app in Trados Studio 2024. Based on the error message you're receiving, it seems like there might be an issue with the authentication process.

Here are some steps you can follow to troubleshoot this issue:

Step 1: Ensure that you are using the correct RWS login credentials. These should be the same ones you use to log into Trados Enterprise.

Step 2: If you are presented with a Registration screen asking for user details when you log into Trados Enterprise, complete the form and submit the update.

Step 3: Try to configure the Language Weaver Provider app again using the same credentials.

Step 4: Make sure that your Trados Studio 2024 is up to date. You can check for updates within the application.

Step 5: If the problem persists, you may need to reinstall the Language Weaver Provider app. You can do this by visiting the RWS AppStore and downloading the latest version of the app.

I hope these steps help you resolve the issue. If you continue to experience problems, please provide more details about the issue and I'll do my best to assist you further.

Best regards,

RWS Community AI

Emma Goldsmith that is no good at all.

Can you log in when you access Language Weaver portal: translate.sdl.com/login

And when wanting to authenticate via the plugin, are you already logged into your Language Cloud account if you look top right of Studio?

Are the details you used to log into LW portal - the same you use in Trados Studio when accessing Language Cloud?

If all of that is as it should be (presumably you had it all working in Trados Studio 2022) then another thing to try is:

Close Studio
Locate: C:\Users\username\AppData\Roaming\Trados\Trados Studio\Studio18
Remove: LanguageCloudMachineTranslation.bin as well as TranslationProviderCredentialStore.bin/2

Let me know your findings

Lyds

Hi Lydia Simplicio . I still have no access...

Can you log in when you access Language Weaver portal: translate.sdl.com/login
No, a message in red says: "You are not allowed to login to Language Weaver"

when wanting to authenticate via the plugin, are you already logged into your Language Cloud account if you look top right of Studio?
Yes

Are the details you used to log into LW portal - the same you use in Trados Studio when accessing Language Cloud?
Yes

presumably you had it all working in Trados Studio 2022
I'm not sure. I don't use NMT usually, although I did have a subscription for testing purposes a while back. My current version of 2022 doesn't have a LW app. 

Remove: LanguageCloudMachineTranslation.bin as well as TranslationProviderCredentialStore.bin/2
I deleted the first file, but the second wasn't there. 
When I reopened Trados 2024, this appears (see screenshot). The last two TM providers in the list are new entries I haven't seen before. I logged in again to my Language Cloud account, and the error message is still there.
 

Dear Emma,

I have just tested the Language Weaver Provider in Studio 2024.

Everything is functioning smoothly. As you can see from the screenshot:

Joe Zhou thank you for confirming all is ok on your end.

From Emma Goldsmith answers I can tell this is a local account related - I will get the help you need Emma.
Especially given:

Emma Goldsmith said:

Can you log in when you access Language Weaver portal: translate.sdl.com/login
No, a message in red says: "You are not allowed to login to Language Weaver"

Emma Goldsmith 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 : 00858532 .

Thanks for logging a support case, Lydia Simplicio .
My account issue is now fixed and I'm up and running with LW.
Cheers,
Emma

Wonderful Emma Goldsmith thanks for letting me know
For future reference what was the issue?

A user account glitch (possibly caused by beta testing in the past).