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

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.

Parents Reply Children