• State Verified Answer
  • Replies 11 replies
  • Subscribers 4 subscribers
  • Views 7442 views
  • Users 0 members are here
Options

Issue with language weaver. We finished building an API for project creation and while we were able to access the TMs were the server with no issues, the API disables the connection to Language Weaver MT. Any ideas what could be causing the disabling dur

Rob Zuvich

All earlier conversations:

Romulus Crisan

I had a look at the source file you sent via email and your problem might be related to the way the credentials are added to the project. If this are not correct the TM will not be enabled. Based on the uri you have on the template you add one or two type of credentials. The second doesn't seem to be a valid language weaver credential since you need to provide the API key.

Rob Zuvich

Hi Romulus,   I added the key for the language weaver bu the translate task is failing now. This is the log I can see

 

Rob Zuvich

2015-03-02 09:56:58,722 [14244] INFO  Sdl.Enterprise2.Platform.Client.Discovery.DiscoveryInfo [(null)] <(null)> - GetServiceUri(identity.svc), preferredScheme(net.tcp), discoveryScheme(http), tokenType(CustomUser)   2015-03-02 09:56:58,732 [14244] INFO  Sdl.Enterprise2.Platform.Client.Discovery.DiscoveryInfo [(null)] <(null)> - 2/Returning nygroupshare01/.../identity.svc   2015-03-02 09:56:58,732 [14244] INFO  Sdl.Enterprise2.Platform.Client.Discovery.DiscoveryInfo [(null)] <(null)> - GetService

 

Romulus Crisan

First of all can you please create a proper forum thread to have this discussion? The activity messages are not meant for this.  I'm a bit confused since my understanding was that you are using language weaver not groupshare. You should than add the groupshare credential only when that's the case - corresponding if branch. Also you are building a language weaver uri which you are not using.
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Yes .. you are correct that issue is with the language weaver.
    We are adding 2 server tms and a language weaver ... for each server tm, we are adding groupshare credentials and for language weaver we are adding its key as the credentials.

    No, we are not adding any language weaver which should not be used.
  • 0 in reply to Rob Zuvich
    So you're going to have 3 translation providers in the end. Now that you've corrected the language weaver is it still disabling?

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/

  • 0 in reply to Romulus Crisan (former member)
    Romulus,
    We found out that it seems that Trados is using during the creation process the settings from 'All Language Pairs' opposed to the specific language pair, where we have specific settings from our templates.

    I modified the templates to read the TMs and SDL BeGlobal from "All Language Pairs" instead from specific language pairs, and settings remained the same during the project creation as to 'Enable', Lookup', etc.. and SDL BeGlobal is no longer getting disabled. However, the pre-translation settings are still being modified (not reading from the templates even from 'All Language Pairs'). That is, template settings for 'Minimum match value', 'Apply automated translation' when no match found applied are the default ones, not from the template.

    I am sending you two projects we just created to illustrate that along with the template files (sdltpl) we are using via email. Since you already have the code, perhaps seeing the Project results/templates will help you to better understand what the issue is, that is, "pre-translation" step failing and template settings being modified during the project creation process.

    Seems that the API connects fine SDL BeGlobal from 'All Language Pairs' so I am assuming the issue goes back to the pre-translation step now. We will be able to confirm that once the API respects the settings from the templates if AT is then pre-populated.

    If you can further take a look and get back to us. Thank you in advance.
  • 0 in reply to Marcia Pedroso
    Romulus, just another observation is: the file does not get pre-translated if SDL BeGlobal is added as a provider. If SDL BeGlobal is removed, then file gets pre-translated with matches from other language providers.
    So even though SDL BeGlobal is no longer being disabled during the project creation process, it seems connection is not being established, and it prevents the file from being pre-translated by other enabled providers.
Reply
  • 0 in reply to Marcia Pedroso
    Romulus, just another observation is: the file does not get pre-translated if SDL BeGlobal is added as a provider. If SDL BeGlobal is removed, then file gets pre-translated with matches from other language providers.
    So even though SDL BeGlobal is no longer being disabled during the project creation process, it seems connection is not being established, and it prevents the file from being pre-translated by other enabled providers.
Children