To add a few remarks:

When you try to unlink the language resource in question from a TM created by the script, you just get the same error message.

When you try to link another language resource, you get the same error message.

Could the PowerShell script (just using the Studio assemblies) anyhow try to create a new language resource, overwriting an existing one with attached language directions?

To clarify: We create TMs using the API. During creation, the TMs are linked to existing language resources. If a language resource is afterwards changed on GroupShare directly and these changes are to be propagated, there is the above mentioned error message.

The possibility of changing language resources should be given. How can this be achieved?

Thanks for your much needed support.

Hi Simon,

I tried with the following C# code, it works fine. The code add a new variable to the language resource. For powershell it is the same. Hope this works fior you too.

public void Test()

{    

   var uri = new Uri("http://mygs");

   var server = new Sdl.LanguagePlatform.TranslationMemoryApi.TranslationProviderServer(uri, false, "sa", "sa");

   const string tmPath = "/rTM";

   var tm = server.GetTranslationMemory(tmPath, Sdl.LanguagePlatform.TranslationMemoryApi.TranslationMemoryProperties.All);

   var languageTemplate = tm.LanguageResourcesTemplate;

   var bundle = languageTemplate.LanguageResourceBundles.First();

   bundle.Variables.Add("TestAddNewVariable");

   languageTemplate.Save();

}