Unexpected exception when initializing task, using server TMs on Groupshare 2017 server. failed to initialize translation engine follows.

Question

Dear SDL Devs and Community, 
 
 we are using the API of the latest Trados Studio 2019 with server based TMs on a GS 17 server and keep running into the following problem. 
 
 We have an existing sdlproj project. This project was created based on a project template which had information on Server-TMs on our server URL (gs 2017 server) and uses TMs on this very server. The TMs are thus known by our created project. 
 We have several occurences in our code of similar error messages. The following stack of exception is produced when calling: 
 ProjectPackageCreation projectPackage = project.CreateProjectPackage(Guid manualTaskId, string packageName, string comment, ProjectPackageCreationOptions options); 
 
 What you will see next are the Exception and InnerExceptions of the ProjectPackageCreation object. 
 Unexpected exception when initializing task 'Analyse': Die &Uuml;bersetzungs-Engine 'sdltm.URL/ Organization English (US) - French (France)' konnte nicht instanziiert werden.. Sdl.ProjectAutomation.Core.ProjectAutomationException: Unexpected exception when initializing task 'Analyse': Die &Uuml;bersetzungs-Engine 'sdltm.https://URL/?orgPath=%2F Organization &tmName= Organization English (US) - French (France)' konnte nicht instanziiert werden.. ---> Sdl.ProjectApi.ProjectApiException: Unexpected exception when initializing task 'Analyse': Die &Uuml;bersetzungs-Engine 'sdltm.https://URL/?orgPath=%2F Organization &tmName= Organization English (US) - French (France)' konnte nicht instanziiert werden.. ---> Sdl.ProjectAutomation.Core.ProjectAutomationException: Die &Uuml;bersetzungs-Engine 'sdltm.https://URL/?orgPath=%2F Organization &tmName= Organization English (US) - French (France)' konnte nicht instanziiert werden. ---> System.Collections.Generic.KeyNotFoundException: No identity information found for server 'https://URL/'. bei Sdl.Enterprise2.Studio.Platform.Client.IdentityModel.IdentityInfoCache.ValidateKey(String key) bei Sdl.Enterprise2.Studio.Platform.Client.IdentityModel.IdentityInfoCache.GetIdentityInfo(String key) bei Sdl.LanguagePlatform.TranslationMemoryApi.IdentityInfoCacheCredentialStore.GetCredential(Uri uri) bei Sdl.LanguagePlatform.TranslationMemoryApi.TranslationProviderCredentialStore.GetCredential(Uri uri) bei Sdl.LanguagePlatform.TranslationMemoryApi.ServerBasedTranslationMemoryFactory.GetUserCredentials(Uri translationProviderUri, ITranslationProviderCredentialStore credentialStore) bei Sdl.LanguagePlatform.TranslationMemoryApi.ServerBasedTranslationMemoryFactory.CreateTranslationProvider(Uri translationProviderUri, String translationProviderState, ITranslationProviderCredentialStore credentialStore) 
 
 In preparation of the project package creation step, we try to make sure, that the TMs are available to the project as follows: 
 string credentials = "user=" + tmServer.username + ";password=" + tmServer.password + ";type=CustomUser"; project.Credentials.AddCredential( strTmUri , credentials); project.UpdateTranslationProviderConfiguration(tmConfig); project.Save(); 
 with strTmUri being similar to this: 'sdltm.URL/ English (US) - German (Germany)'

It seems to us, that somehow the login credentials, URL, TM name or a combination of these is wrong. Since we basically are using the demo code from several SDL sources (see links below) it would be great, if you could point out other potential sources of error. 
 
 Our project is huge, new, and does work as expected in general but does not really cooperate well with server based TMs on the GS server. We tried to apply everything the docu states @ http://producthelp.sdl.com/SDK/TranslationMemoryApi/2017/html/50a524b7-e3fe-4ba6-894b-b3959fd3f8ce.htm and of course in the projectautomation API part. Further clarification on your side would be greatly appreciated. 
 
 Best regards, 
 Hendrik, on behalf of the Plunet CAT integration team 
 
 We already used these resources describing similar problems and TM handling: 
 https://community.sdl.com/developers-more/developers/language-developers/f/api_qa_-_sdl_tms/12877/how-to-use-analyzefiles-pretranslate-tasks-with-server-based-translation-memory 
 https://community.sdl.com/developers-more/developers/language-developers/f/sdk_qa/1013/analyzefiles-and-pretranslatefilestasks-inproject-automation-api-ignore-server-tms 
 https://gist.github.com/cromica/e1a976fdfdc821136c7610b5e984904e 
 https://github.com/sdl/trados-studio-api-samples/tree/master/LanguagePlatform/Sdl.SDK.LanguagePlatform.Samples.TmAutomation 
 http://producthelp.sdl.com/SDK/TranslationMemoryApi/3.0/html/646950ef-d135-46dd-a2cf-1c4ebf57ec94.htm

Patrick Andrew Hartnett · Accepted Answer

Hi Laurent Hug , sorry to hear this. 
 I can confirm that during my tests, I was able to reproduce the same exception message that you received initially; I discovered that the root exception was related to a discrepancy in the version of System.Net.Http ; the solution was to make specific reference to that assembly as opposed to pulling it from the GAC. 
 What is the full version of Studio 2019 that you are using in your automation environment? 
 Lets try the following: 
 
 I will prepare and provide your team with the automation sample project that I coded where this is working interrogating your GS 2017 server, against the latest production release of Studio 2019 SR2 CU8 that I have locally. I will update you via e-mail either later on today or tomorrow morning. 
 Try the test without any other plugins from being loaded with the automation Studio environment, to exclude any external influences (e.g. unknowns)

Patrick Andrew Hartnett · Answer

Hi Guys, I have investigated this issue this morning and identified the root cause. It seems that there is an issue in resolving the correct version of System.Net.Http assembly; the original exception is getting gobbled up with abstraction, which was preventing us from understanding the root cause in this case. You can work around this by simply making a hard reference to the same version of this assembly (that Studio 2019 is using) in your automation project. 
 Add this reference to your project: C:\Program Files (x86)\SDL\SDL Trados Studio\Studio15\System.Net.Http.dll

Patrick Andrew Hartnett · Answer

Hi Hendrik, 
 Sorry to hear you are still having problems in getting this running on your system. You are right, my mistake, that dll doesn't seem to be included with the installer anymore. 1. There should be no difference with choosing one overload over the other for ProjectCredentials.AddCredential. 
 2. I have just checked now and the version of System.Net.Http that I&rsquo;m using locally for Studio 2019 is 4.3.3, available for download here https://www.nuget.org/packages/System.Net.Http/4.3.3 Download/extract and make a hard reference to the untimes\win\lib
et46\System.Net.Http.dll from that package 
 let me know how it goes, 
 P.

Paul · Answer

Hendrik Striepe 
 Please create a separate post for this. We cannot manage never ending threads on multiple topics. They're also unhelpful for other users.

GroupShare Developers > GroupShare Developers forum

Unexpected exception when initializing task, using server TMs on Groupshare 2017 server. failed to initialize translation engine follows.

Top Replies