Hi Alison Watt

Can you please check this link https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039435 as It might help

Best regards, 

Loredana 

Hi Loredana

It is not listed here, 

So I went to C:\Users\aliso\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages as instructed and renamed it 'Studio Subtitling_old' - is this correct?

Update: I have now removed it from this folder and Trados opens. But the thing is ultimately I don't want to uninstall it, I need to use it! Suggestions?

Alison

If you can advise us how you solved this Alsion, that would be great!

Thanks.

Sameh

I did all of your suggestions by the way, but in vain Paul. I renamed to Studio16_old to recreate from scratch, but also the same error and I can not even access the integrated Appstore from within SDL Studio

Sameh Elsharkawy

Renaming Studio16 won't help if your problem is plugin versioning..  You need to also remove your plugins properly and reinstall with the appropriate version from the appstore for your version of Studio.  Rename this one:

...\AppData\Roaming\SDL\SDL Trados Studio\16

Then also rename Studio16 to make sure anything you keep putting back there which could influence this problem is reset.

Only this solution worked Paul, for both the Weaver and the Subtitling plugins, so the pain of installing my full set of plugins REMAIN! Thanks for your help on this, but indeed this has nothing to do with my amazing setup as you mentioned, but it has to do with the mechanism SDL Studio is dealing with plugins every time there is an update or cumulative batch or a new service release. I can not imagine how plugins would have any contradiction if they are tested to work together side by side. Also I can not imagine that having other SSD drives or many partitions would impact the behaviour of SDL Studio. Anyway, thanks a lot for your support on this. SDL should be proud of someone like you who jumps to the rescue.

Renaming this: ...\AppData\Roaming\SDL\SDL Trados Studio\16

is the solution then.

Alison, fear not, this will do the job, so time to give your labtop a break. 

Sameh

I am about to install the MT Enhanced plugin Paul and to the best of my knowldege and that of the Worldbank colleagues, we always used an old version of the plugin which was the only one that worked. Now I am going to test the new one from the integrated appstore and see how it works. I hope this does not waste the remainder of my day, as I do have some translation work to finalize. Most of the people I trained at the WB complained that the new plugin was not working for them, so are you aware of this issue? 

Sameh Elsharkawy

Thank you for the video.  The very first thing a support engineer will do is reset Studio (this includes plugins) which you have still not done.  So you should relly do this properly first and if you still can't run Studio without any error after removing all external influences such as plugins then we have something to help resolve.

If Studio does work, then start reinstalling by just taking the "problematic" plugins and see if the issue is still there.

here we go again Paul! This updated plugin, installed via the integrated Appstore does not work, and I believe this has nothing to do with Microsoft, as if I try to install the old plugin, it will work, so it has nothing to do with the credentials, API key or Microsoft Key or the Category ID! Or maybe is, it is something in between both SDL and Microsoft? I have no idea. Any help? I just talked to Osama Abdul Hameed, the Worldbank Arabic division team leader and he confirmed the same, not only with him but all other Worldbank translators. 

but I did Paul, haven't you checked all my messages? including this one about the MT Enhanced Plugin?

Sameh Elsharkawy

Sameh Elsharkawy said:

I can not imagine how plugins would have any contradiction if they are tested to work together side by side.

Well... of course this does not happen!  There are hundreds of plugins on the appstore and we do not install every single one to see what happens and make sure they all work together.  That sort of testing is simply not sustainable, especially since developers are free to update their own plugins whenever they wish.

Sameh Elsharkawy said:

Also I can not imagine that having other SSD drives or many partitions would impact the behaviour of SDL Studio.

You only have to look in the knowledgebase to know that this can have an impact.  I am often amazed at what can cause a problem on a computer!

Sameh Elsharkawy said:

the pain of installing my full set of plugins REMAIN!

Perhaps it's a good time to take on a new strategy?  Installing plugins today is really a very simple process.  You do have to restart Studio but the act of installing or deleting a plugin is very simple.  So perhaps you should not install them all, but rather install what you need.  I'm sure you can't use all of the plugins you have installed every day and for every project.  Or do you?

Sameh Elsharkawy said:

Only this solution worked Paul, for both the Weaver and the Subtitling plugins

Phew!  That is the best news I've had today!