Problem using Antidote 11 and 12 with Trados 2024

Hi,

Could you please provide me with Antidote Verifier version 4.0.2.0

That is the only version that will now work for me.

I tried unsuccessfully to install Antidote 12. I lost access to Antidote and had to uninstall Antidote 12 and reinstall Antidote 11.

Now, I can't get the Antidote Verifier 4.0.3.3 plugin to work anymore. I have tried dozens of times to remove the Antidote Verifier 4.0.3.3 plugin and it keeps reappearing in my list of Installed plug-ins in Trados 2024.

When I try to install the latest plugin, Trados will not boot up anymore. I have to go and manually and delete the files (AppData\Roaming\Trados\Trados Studio\18\Plugins\) to regain access to Trados 2024.

Trados also crashes when I copy the plugin file directly into the Packages folder (AppData\Roaming\Trados\Trados Studio\18\Plugins\Packages\).

Trados 2024 will not allow the Antidote Verifier version 4.0.3.3 to be uninstalled. It never disappears from the list of Installed plugins.

I tried a full uninstall and reinstall of Trados 2024 and tried the repair funcion as well.

My hope is that the older Antidote Verifier versoin 4.0.2.0 will get Antidote working again in Trados 2024, as I was able to do that once before.

Ian Rahn

emoji
  • Hi  

    Can you access this link: Version 4.0.2.0

    However you cant install a legacy version when you are still struggling to remove the later 4.0.3.3

    In the meantime I see you have a previous post here: Does the Antidote Verifier plugin support the new Antidote 12? and  did ask for input as the issues seem local to you.
    I also tried to reproduce what you descried so far as manually copy/past/delete from AppData\Roaming\Trados\Trados Studio\18\Plugins\Packages and in all my cases Studio did not crash and the Antidote version 4.0.3.3. did remove/install as expected.

    Seems your Studio version is struggling in more than one way so please may I recommend you try the following:

    Run FreshStart which you can download here
    Goal is to get Studio version 2024 working error free then we can tackle the Antidote concerns.

    Looking forward to next step

    Lyds

    Lydia Simplicio | RWS Group

    _______
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Hi Lydia,

    I tried using FreshStart and reconfigured a newly installed Studio from scratch: now I can't use MultiTerm or Antidote.

    We are at the point that someone will need to take control of my computer remotely to fix this problem.

    Ian

    emoji
  •   I  have logged a support case on your behalf to at least get Studio/MultiTerm working. 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 : 00881843 .

    Lydia Simplicio | RWS Group

    _______
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Hi Lydia,

    It turns out that the installation of the Antidote Verifier had somehow become corrupted.

    The solution entailed NOT having Trados Studio running and running this program:

    C:\Program Files (x86)\Trados\Plugin installer\Sdl.Community.SdlPluginInstaller.exe

    Run the program at that path and click on the "Uninstall" beside Antidote Verifier.

    Then reinstall the Antidote Verifier from the App Store and click on the green link at the top of the AppStore screen prompting you to restart Trados.

    Upon restart, it is very important to note that the icons for Antidote may appear only on the Add On tab rather than on the Review tab. In my case, I now have to run Antidote from the Add On tab, but that's not a big deal. It works the same way as before.

    Using FreshStart did not solve my problem: without running the above SDL Community SDL Plugin Installer app, I would never have been able to completely uninstall the corrupted version of the plugin. 

    Ian Rahn

    emoji