Hi Chris Pulsifer ,

I have added an item on our board to followup on Monday, to confirm if there are any new issues that we are not aware of; internal ref. SDLCOM-3817

Until then, can you please provide me with some additional info, as follows:

• Release version of Trados Studio 2021
• Release version of the SDL MT Cloud plugin
  • Is the plugin signed?
• Error log or exceptions
• If possible, also provide me with the source code of the project automation (phartnett@rws.com)
  • I'm mostly interested in the plugin configuration file

• Trados Studio: 16.2.9.9198
• SDL MT Cloud Plugin: 3.1.3.0
  • not sure if it's signed, how do I check?
• No exceptions logged, everything just seems to work from the code perspective
• Not allowed to post the source code to a community forum, but it's the same source code I shared a month or two ago when working with you on our prior problem.  No longer calling AddBeGlobal() method in that source, just a new function to push the SDL MT credentials into the project
  • Where would I find the plugin configuration file?

Found a way to download externally, confirmed that the plugin that I already had is the same as the plugin that Paul pointed me to.  Continuing to work with Patrick's sample code to test.

Chris Pulsifer 

Chris Pulsifer said:

That is the file that I checked for a digital signature.

Understood.  When we talk about signed plugins we are talking specifically about plugins signed so they don't cause this warning in Trados Studio:

When I build and run the code that Patrick pointes to get the following:

Program running emits these status messages:
Scan: Completed
ConvertToTranslatableFormatTask: Completed
CopyToTargetLanguagesTask: Completed
RunAnalyzeTaskFiles: Failed
RunPreTranslateFiles: Failed

When I open the project in Studio, I get a popup message::

"The language translation provider "Language Weaver provider" could not be opened and has been disabled."

Tried installing the copy I downloaded today and now I get "Service:"SDL. 'Desktop.Platform.CommandBars.IActionService' could not be started" and Studio shuts down.

Hi Chris Pulsifer , sorry to hear you're haveing issues with this setup. 

This sounds like the version of the plugin installed is not compatible with the version of Trados Studio. can you check and tell me what is the exact version of Trados Studio you have installed / testing against.

Chris Pulsifer 

On this bit...

Chris Pulsifer said:

Tried installing the copy I downloaded today and now I get "Service:"SDL. 'Desktop.Platform.CommandBars.IActionService' could not be started" and Studio shuts down.

This is a Studio problem, often resolved by using reset window layout.If it doesn't help then reset Studio.  To do this just close Trados Studio and then rename this folder:

c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\Studio16\

to c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\Studio16_old\

Finally restart Trados Studio and try again.

It might also be worth deleting the plugin from the plugin folders (packed and unpacked) first, then reinstalling after the reset.  Sometimes, depending on how you installed, the unpacked from a previous version can remain in place.  So a proper clean out would be advisable.

Patrick Andrew Hartnett 

Trados Studio 16.2.9.9198
Language Weaver MTCloud 4.2.18.3

Hi Chris Pulsifer , oki; these should be compatible, however, I'd recommend upgrading to the latest CU 12 for 2021 (i.e. 16.2.12.9338)

in this case, as Paul suggested, I'd check and clear out any existing versions of the plugin from the roaming directories.  Might be a conflict trying to load two different versions of the same plugin guid into the Studio context

Got it built and producing a project with successful pre-translation.  When I open the published project, I get a message that the Language Weaver provider can't be started and will be disabled.  When I view the translation, the segments all show NMT though, so it appears to have worked.  Will try to compare sample code to our application.

Hi Chris Pulsifer , that's awesome news, thanks for confirming this.  The only thing that comes to mind for the remaining problem is to check that you are using the same version of the Language Weaver plugin (+ studio) on the machine where you are opening the project created from automation.

Great news that it's working in automation though; well done (y)

Unfortunately(?), I am opening the project on the same machine that I am running the code on, so I know the versions are the same.  Checking for other possible issues

Unfortunately(?), I am opening the project on the same machine that I am running the code on, so I know the versions are the same.  Checking for other possible issues

 Patrick Andrew Hartnett 

Trying to make the sample code work with our processing model.  We use language/project specific templates as part of our workflow.  Our process is to pre-translate as much as possible from our TMs and then use NMT to translate remaining un-processed content.  I have added the following ot the sample code:

ProjectTemplateReference template = new ProjectTemplateReference(@"C:path\to\template");
var project = new FileBasedProject(projectInfo, template);

<LanguageDirections>
<LanguageDirection Guid="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" SettingsBundleGuid="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" TargetLanguageCode="de-DE" SourceLanguageCode="en-US">
<AutoSuggestDictionaries />
<CascadeItem OverrideParent="true" StopSearchingWhenResultsFound="false">
<CascadeEntryItem PerformConcordanceSearch="true" Penalty="0" PerformUpdate="true" PerformNormalSearch="true">
<MainTranslationProviderItem Uri="sdltm.">njp1grpshgd01.corp.bloomberg.com/ Enabled="true" />
</CascadeEntryItem>
<CascadeEntryItem PerformConcordanceSearch="true" Penalty="0" PerformUpdate="false" PerformNormalSearch="true">
<MainTranslationProviderItem Uri="sdltm.">njp1grpshgd01.corp.bloomberg.com/ Enabled="true" />
</CascadeEntryItem>
<CascadeEntryItem PerformConcordanceSearch="false" Penalty="0" PerformUpdate="false" PerformNormalSearch="true">
<MainTranslationProviderItem Uri="sdlmtcloud:///" State="{"AutoSendFeedback":true,"LanguagesSupported":[{"Name":"English (United States) - German (Germany)","SourceTradosCode":"en-US","TargetTradosCode":"de-DE","SelectedSource":{"CodeName":"eng","IsLocale":false},"SelectedTarget":{"CodeName":"ger","IsLocale":false},"SelectedModel":{"DisplayName":"eng-ger Bloomberg","Model":"bloomberg","MTCloudLanguagePair":{"sourceLanguageId":"eng","targetLanguageId":"ger","model":"bloomberg","displayName":"Bloomberg","name":"engger_bloomberg","active":"yes"},"Source":"en-US","Target":"de-DE"},"SelectedDictionary":{"name":"No dictionary available","description":null,"source":null,"target":null,"dictionaryId":""},"SourceLanguages":[{"CodeName":"eng","IsLocale":false}],"TargetLanguages":[{"CodeName":"ger","IsLocale":false}]}],"ResendDraft":true,"SendFeedback":true}" Enabled="true" />
</CascadeEntryItem>
</CascadeItem>
</LanguageDirection>
</LanguageDirections>

The machine url for the sdltm entry is valid and reachable form the machine running the program.

Hi Chris Pulsifer ,  I'm not sure if there is a rendering issue with presenting the content in your example above, but those uri strings seems to be broken (e.g. <MainTranslationProviderItem Uri="sdltm.">njp1grpshgd01.corp.bloomberg.com/ Enabled="true" />)

Can you provide me with the template you are using?  to phartnett@sdl.com

Hi Chris Pulsifer , to avoid scope creep with issues on the community.  I'd recommend to create a new issue, indicating in the subject that you are not able to connect to a GroupShare TM resource via Project Automation and we can now close this issue "SDLMTCloud...", as you have confirmed the solution working.  wdyt?

Yes I think this can be closed