• State Suggested Answer
  • +2 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 393 subscribers
  • Views 2667 views
  • Users 0 members are here
Options
Related

Automatic analysis task fails in Studio 2022 when using TM with Chinese characters

Bram van der Steen

Hello,

We are experiencing Sdl.ProjectApi.AutomaticTasks.Analysis failing when using TMs containing Chinese characters. This is somewhat similar to the issue brought up here:  [Help needed] Trados Studio 2021 API Error：The type initializer for 'Sdl.Core.LanguageProcessing.ICU2.WordBoundaryFinder' threw an exception.
In this case though, no exception is thrown, but the task simply returns with the failed status and the message "One or more errors occurred", which sadly does not tell us a lot about what the problem might be.
We have also already implemented the solution to the linked issue in our program.

In my own system, this problem began to occur after updating my Trados Studio 2022 version from 17.0.4.13209 to 17.0.6.14902.

Any help is greatly appreciated.

Best regards,
Bram van der Steen
emoji
Rate translation
×
Suggest better translation
×
Parents
  • +2

    Hi , , It appears that we'll need to add another binding redirect to resolve dependency changes against the latest releases.

    Please add both of these binding redirects to your app.config file and let me know if it resolves the issue.

    <dependentAssembly>
  <assemblyIdentity name="icu.net" publicKeyToken="416fdd914afa6b66" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-2.7.0.0" newVersion="2.7.0.0" />
</dependentAssembly>

<dependentAssembly>
	<assemblyIdentity name="Microsoft.Extensions.DependencyModel" publicKeyToken="adb9793829ddae60" culture="neutral" />
	<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

    emoji
Reply
  • +2

    Hi , , It appears that we'll need to add another binding redirect to resolve dependency changes against the latest releases.

    Please add both of these binding redirects to your app.config file and let me know if it resolves the issue.

    <dependentAssembly>
  <assemblyIdentity name="icu.net" publicKeyToken="416fdd914afa6b66" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-2.7.0.0" newVersion="2.7.0.0" />
</dependentAssembly>

<dependentAssembly>
	<assemblyIdentity name="Microsoft.Extensions.DependencyModel" publicKeyToken="adb9793829ddae60" culture="neutral" />
	<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

    emoji
Children