Hi Michal Souček ,

I'm checking this on my side and there is no error that is triggered immediately, so I assume must be something locally, perhaps.

Can you try using the plugin on a different project, and check if it works as expected with a different project/different files?

If it works correctly on other projects, then we know the culprit. What you can do is remove it from the project, recreate it , then add again the plugin.

If the plugin fails for all projects/files, I would advise checking the plugin version, remove it and add it again from the integrated appstore inside Studio.

Remove the plugin from these paths:

c:\Users\onagy\AppData\Roaming\Trados\Trados Studio\17\Plugins\Packages\

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

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

c:\ProgramData\Trados\Trados Studio\17\Plugins\Packages\
C:\ProgramData\Trados\Trados Studio\17\Plugins\Unpacked\

Does it help?

Regards,

Hi Michal Souček ,

I'm checking this on my side and there is no error that is triggered immediately, so I assume must be something locally, perhaps.

Can you try using the plugin on a different project, and check if it works as expected with a different project/different files?

If it works correctly on other projects, then we know the culprit. What you can do is remove it from the project, recreate it , then add again the plugin.

If the plugin fails for all projects/files, I would advise checking the plugin version, remove it and add it again from the integrated appstore inside Studio.

Remove the plugin from these paths:

c:\Users\onagy\AppData\Roaming\Trados\Trados Studio\17\Plugins\Packages\

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

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

c:\ProgramData\Trados\Trados Studio\17\Plugins\Packages\
C:\ProgramData\Trados\Trados Studio\17\Plugins\Unpacked\

Does it help?

Regards,

Hello Oana,

thanks for quick reply. Unfortunately it is not working in other projects as well. I tried complete removal of the plugin including deleting it from mentioned paths and after reinstalling I am receiving still the same error message.

Meanwhile during work I have noticed, that sometimes I am receiving the same message for the translation provider "AnyTM". Looks like this message does not appear with each "touch" with TM, just occasionaly. Since I was using these TMs only for concordance, it was not so serious issue to me and I have always just deleted the message. So it looks lika an issue of Studio handling the translation providers. As I mentioned, I also tried complete "repair" of Studio, but without success. :-(  

Hi Michal Souček ,

I see, thank you. We'll look into this further to see if there's a correlation between the plugin and the Studio core components and if we can fix the app from our side, we'll do it.

Thanks,

Oana

Great, thanks. If you will need some more info, like some logs etc. let me know. The fact, that it occasionally appears also for other (and local) providers like AnyTM or common TM is making me nervous. I am thinking about complete uninstall, delete and install of Studio, but currently I am quite work-overloaded and have no time for playing wit PC.

In the RWS AppStore appeared new version of this plugin declaring to solve this issue and it looks like it is working again. Many thanks for quick analyze and fix.

Note that I had to remove the old version again as recommended, i.e. including deleting the files from above mentioned folders manually, without this it was not fixed.

Michal Souček 

Michal Souček said:

Note that I had to remove the old version again as recommended, i.e. including deleting the files from above mentioned folders manually, without this it was not fixed.

To be expected because the old unpacked folder will prevent the new plugin from unpacking so you end up with no change.