Exception when executing UpdateProjectTm: Unexpected exception when configuring file multiFileConverter for task 'Update Project Translation Memories': Settings not set..

Hi everyone!

I'm using SDL Trados Project Automation API in C#.

When I was using Trados 2011 everything worked like a charm, but when switched to SDL Trados 2014 I got an exception.

I perform following scenario:

  • -create project in Trados with one file and one TM attached
  • set some settings in Trados project
  • generate statistics for project
  • generate package
  • upload return package
  • execute automatic action Update Project Translation Memories.

When executing this automatic action I got following exception:

File: 22e4aac2-8597-4928-a99b-a53b979fbcf4, message:Unexpected exception when configuring file multiFileConverter for task 'Update Project Translation Memories': Settings not set..

Despite I have set all properties related to updating project translation memory, like written in API code examples:

ISettingsBundle settings = project.GetSettings();
    TranslationMemoryUpdateTaskSettings updateTmSettings = settings.GetSettingsGroup<TranslationMemoryUpdateTaskSettings>();
    #endregion 

    #region "NewTranslations"
    updateTmSettings.AlwaysAddNewTranslation.Value = true;
    #endregion 

    #region "Status"
    updateTmSettings.UpdateWithApprovedSignOffSegments.Value = true;
    updateTmSettings.UpdateWithApprovedTranslationSegments.Value = true;
    updateTmSettings.UpdateWithTranslatedSegments.Value = true;

    updateTmSettings.UpdateWithDraftSegments.Value = false;
    updateTmSettings.UpdateWithRejectedSignOffSegments.Value = false;
    updateTmSettings.UpdateWithRejectedTranslationSegments.Value = false;
    updateTmSettings.UpdateWithUnspecifiedSegments.Value = false;
    #endregion 

    #region "UpdateTaskSettings"
    project.UpdateSettings(settings);


Any idea what else should I do to make it working ?
What has change between Trados 2011 and 2014, which could break this funcionality ?

Thanks for help!
Parents
  • Hi,

    I spoke to development on this and it looks like a difference introduced when we added the TM user ID feature.

    The “Settings not set”  refers to the users settings not set, so the TM Update task cannot access the TM user ID.  This is currently only set when you create a new project through the API, but not when you open an existing project or create one from a package.

    The problem can be resolved when creating new projects, but not when updating an existing one which is your usecase.  So you will require a fix from development.  There isn't a delivery date for the fix yet but we’ll update this post as soon as we have one... hopefully sooner rather than later.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • Hi,

    I spoke to development on this and it looks like a difference introduced when we added the TM user ID feature.

    The “Settings not set”  refers to the users settings not set, so the TM Update task cannot access the TM user ID.  This is currently only set when you create a new project through the API, but not when you open an existing project or create one from a package.

    The problem can be resolved when creating new projects, but not when updating an existing one which is your usecase.  So you will require a fix from development.  There isn't a delivery date for the fix yet but we’ll update this post as soon as we have one... hopefully sooner rather than later.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children