• State Verified Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 1365 views
  • Users 0 members are here
Options

Problem with Record Source plugin - translation provider could not be found and has been disabled.

Matthijs Frankena

Hi,

I used Record Source a lot in Studio 2017, and I would like to do so as well in Studio 2019.

However, it doesn't want to work with me. When I set up a project and add a TM through Record Source, after a while, when I open the project again, I get the following message:

"The translation provider '(addsourcetm.sdltm.file:///C:/<full file path to TM>)' could not be opened and has been disabled."

Warning message in Trados Studio stating 'The translation provider could not be opened and has been disabled.' with an exclamation mark icon.

In the project settings, the TM is disabled and all I can do is delete it and add it anew. This poses a second problem: The plugin Record Source has disappeared as well.

Whether it's to do with what I described above I don't know, but the TM (that I had made in 2019, so I would expect it to be compatible with 2019) is now also shown as a TM that needs to be upgraded. 

For now, I leave it as it is: No Record Source in Studio 2019.

Any ideas on how to fix this?

Best regards,

Matthijs

Generated Image Alt-Text
[edited by: Trados AI at 4:38 PM (GMT 0) on 28 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • +1

    My apologies for not coming back to this sooner. I have found the cause of the problem, and therefore the solution.

    Earlier this year I had to reinstall Windows 10, and then of course all my settings were set back to default. Including those for the mouse. Where before I could click a few times on a program shortcut and only one instance would be launched, now multiple instances were started. And with programs like Studio, that need exclusive access to certain files, this would lead to the second instance not being able to load the plug-in and then reporting that it couldn't find the translation provider. Me being unaware of this problem (and of the first instance, which would not have this issue) of course thought the problem was in Studio, where actually it was a PEBCAK issue.

    After adjusting settings for the mouse (not so fast) and myself (perhaps better to rightclick and choose "Open" instead of clicking like mad) this problem has not manifested itself again. Sorry for the misunderstanding and the unnecessary question.

    Matthijs
Reply
  • +1

    My apologies for not coming back to this sooner. I have found the cause of the problem, and therefore the solution.

    Earlier this year I had to reinstall Windows 10, and then of course all my settings were set back to default. Including those for the mouse. Where before I could click a few times on a program shortcut and only one instance would be launched, now multiple instances were started. And with programs like Studio, that need exclusive access to certain files, this would lead to the second instance not being able to load the plug-in and then reporting that it couldn't find the translation provider. Me being unaware of this problem (and of the first instance, which would not have this issue) of course thought the problem was in Studio, where actually it was a PEBCAK issue.

    After adjusting settings for the mouse (not so fast) and myself (perhaps better to rightclick and choose "Open" instead of clicking like mad) this problem has not manifested itself again. Sorry for the misunderstanding and the unnecessary question.

    Matthijs
Children
No Data