I'm in exactly the same position...I have tried everything but cannot get MT/Language Weaver to work. I did however get an error:

After which Language Weaver was removed from the list of TMs and it now cannot be added.

I am pretty desperate now after wasting several hours with several deadlines looming... any help much appreciated!

Amy Barter Alexandra Stephens 

I suggest you remove the plugin altogether and then reinstall it from the integrated appstore to make sure you have the latest version installed for 2021.

Also worth noting that you can get MT from Language Weaver without using the plugin at all:

Once signed in you will see this... just select Machine Translation:

Does that work for you?

Hi Paul,

Thanks ever so much for your advice but I'm afraid that I've already tried uninstalling the plug-in and reinstalling it from the integrated app store (twice in fact) but it made no difference. If I try opening Language Weaver via the method you've shown above, I simply get the following error message when I click on 'Cloud-based resources':

I don't suppose you have any other suggestions at all? Thanks! Amy

Hi Paul,

Thanks ever so much for your advice but I'm afraid that I've already tried uninstalling the plug-in and reinstalling it from the integrated app store (twice in fact) but it made no difference. If I try opening Language Weaver via the method you've shown above, I simply get the following error message when I click on 'Cloud-based resources':

I don't suppose you have any other suggestions at all? Thanks! Amy

Amy Barter Alexandra Stephens 

You could try working with the previous version of the plugin.  I'd make sure the old ones were completely removed first though, so close Studio and then delete these:

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages\Language Weaver.sdlplugin

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\Language Weaver\

Then download version 4.2.18.3 from here:

 Archived Versions: Language Weaver 

Unzip it and install it.  Restart Studio.

I just went through this whole exercise myself and this works.  Looks like there is a problem with the new version of this plugin so I will change it on the appstore untl we fix it.  But for now please use this version from the wiki.

Woohoo! It worked! Thanks so so much for your help Paul!

Amy Barter 

Excellent... I have also replaced the one on the appstore too, so you won't get notifications to update it and anyone else looking for this won't have a problem.

Thank you for this, it worked!! Hurray!

Amy Barter Alexandra Stephens 

Just letting you know that the plugin was updated this morning so if you see a notification it is safe to update!

Great, thanks for the info Paul :-)

Just a follow-up on this... I updated the plugin again this morning and have the same issue all over again... just so you know! Thanks again for your help Paul

Hi Alexandra Stephens ,

Can you please remove the plugin from all of these folders:

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages\
c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\

c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\16\Plugins\Packages\
c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\16\Plugins\Unpacked\

c:\ProgramData\SDL\SDL Trados Studio\16\Plugins\Packages\
c:\ProgramData\SDL\SDL Trados Studio\16\Plugins\Unpacked\

After that, try again to install it from the integrated appstore.

Hopefully this will fix it 

Regards,

Amy Barter Alexandra Stephens 

Just to confirm what Oana advised.  I just tested this and had the same problem.  But it is just a one off caused by the changes made in the plugin namespace.  You just need to close Studio and only delete this folder (as long as you didn't put the old one back):

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\Language Weaver\

Then restart and all will be well.

One other thing to note is that the first time you add the provider to a project you may be asked to sign in even though you are already signed into Studio.  This will also only happen once, also a side effect of some wide ranging changes we made to support alternative logging in methods.

You should take this upgrade though because all future updates will have this same problem for you UNTIL you take the leap!