Termbase Viewer in SDL Trados Studio displaying script error: 'An error has occured in the script on this page' - Method not found: 'System.Object Sdl.MultiTerm.Client.UI.Viewer.ScriptingHost.Search(System.S...

Article Number:000007275 | Last Updated:10/29/2018 10:06 AM

Scope/Environment

SDL Trados Studio 2017 SR1
SDL MultiTerm 2017 SR1

Symptoms/Context

After installing Cumulative Update 6 for SDL MultiTerm 2017 Service Release 1, when trying to modify terms in the SDL Trados Studio Termbase Viewer dialog in the Editor view the following error message is displaying:

Script Error
An error occurred in the script on this page
Line: [number]
Char: [number]
Error: Method not found: 'System.Object Sdl.MultiTerm.Client.UI.Viewer.ScriptingHost.Search(System.String, System.String, Int32, Boolean, Boolean)'
Code: 0
URL: file://C:/Program%20Files%20(x86)/Common%20Files/SDL/MultiTerm14/Editor/modern/bundle.js

Do you want to continue running scripts on this page.

User-added image

Resolution

Solution 1:

Run Powershell script

Close all SDL applications.
Download the *.zip attached to this Knowledge article.
Extract the content which contains a PowerShell script with the extension *.ps1 and the Sdl.MultiTerm.Client.UI.dll
Right-click file AllLanguages3264+UpdateStudioForMultiTermCU6.ps1 and select Properties.
If a check-box Unblock is displayed, select this option.
Click OK.
Right-click the AllLanguages3264+UpdateStudioForMultiTermCU6.ps1 and select Run with PowerShell. A Windows PowerShell dialog where you can see that files are copied will open.
After the copying process is finished, close the PowerShell dialog and start SDL Trados Studio.

Note: Above steps assume that your PowerShell Execution Policy is set to RemoteSigned or less restrictive. If this is not the case, refer to below workaround.

Solution 2:

Run PowerShell script (by-passing Execution Policy)

Close all SDL applications.
Download the *.zip attached to this Knowledge article.
Extract the content which contains a PowerShell script with the extension *.ps1 and the Sdl.MultiTerm.Client.UI.dll
Run Windows PowerShell as administrator (default location: C:\Windows\System32\WindowsPowerShell\v1.0)

Run following command:

Set-ExecutionPolicy ByPass -Scope Process

When prompted, confirm by pressing [Y] key
Run following command (where <folder> is the folder where the PowerShell script is located):
```
cd "<folder>"
```

Run following command:

.\AllLanguages3264+UpdateStudioForMultiTermCU6.ps1

After the copying process is finished, close the PowerShell dialog and start SDL Trados Studio.

Note: Above steps may not work if the PowerShell Execution Policy is set via Group Policy. In this case, contact your Administrator.

Solution 3:

If Studio has already been updated to SDL Trados Studio 2017 SR1 - 14.1.10014.38031 only replace the DLL for MultiTerm

Close all SDL applications.
Download the *.zip attached to this Knowledge article.
Extract the content which contains a PowerShell script with the extension *.ps1 and the Sdl.MultiTerm.Client.UI.dll
Ignore the PowerShell script and instead simply replace the Sdl.MultiTerm.Client.UI.dll found in
C:\Program Files (x86)\SDL\SDL MultiTerm\MultiTerm14
with the one extracted in step 3

Root Cause

SDL Trados Studio uses parts of the SDL MultiTerm Desktop *.dlls (if both Studio and MultiTerm are installed) . The Cumulative Update 6 for SDL MultiTerm Desktop update some of these shared components, which however caused that SDL Trados Studio runs into versioning issue and cannot handle the "new" components. This is leading to the error described in the symptoms section.

The development is working on a update/patch which will be released with the Cumulative Update. Until a permanent solution is in place, you can apply the workaround described in the Resolution section.

Note: This issue has already been fixed for Studio in Cumulative Update 14 for SDL Trados Studio 2017 SR1 (Build 14.1.10014.38031, Released on 10 October 2018). If CU14 has been installed for Studio already, please apply Solution 3, to also fix the issue in MultiTerm.

Reference

CRQ-10156

Attachments

PowerShellWorkaround.zip

Send Article Feedback