Hi Helene Minville ,

Maybe the server had been registered before in your MultiTerm. Go to File > Setup > Servers and remove the server, if shown there.

HTH

Best regards

Annette (from Manfred's account) 

I am not connected to any server. 

When I right-click "open with Multiterm" on my TB file I get this mesage on the app:

***

Error processing command line arguments: Object reference not set to an instance of an object.

USAGE: MultiTerm.exe [/help|/?] /arg1 val1 /arg2 val2

Task: NoAutoUpdate
Description: Starts the application without automatically checking for updates.
Usage: MultiTerm.exe /noautoupdate
Arguments:
/noautoupdate Starts the application without automatically checking for updates.

Task: Opens a specific remote connection
Description: Allows specification of communication settings on startup.
Usage: MultiTerm.exe /s <server>
Arguments:
/s Switch to specify a business server at startup.

Task: Allows opening settings template files on startup
Description: Open a settings template file
Usage: MultiTerm.exe /st <file.sdlmttpl>
Arguments:
/st Switch to open a settings template at startup.

Task: Open Termbases, Entries, Languages and Terms
Description: Allows opening termbases, entries, languages and terms on startup
Usage: MultiTerm.exe /tb <termbase> [/e <entry1> [<entry2> ...]] [/t <term>] [/si <source index>] [/ti <target index>]
Arguments:
/tb Switch to open a termbase at startup.
/e Switch to open entry with number at startup.
/t Switch to search for a term at startup.
/si Switch to set a source language at startup.
/ti Switch to set a target langu

Helene Minville 

Try closing Multiterm, deleting all of these folders, and then restart:

%APPDATA%\Trados\MultiTerm\MultiTerm17\

%PROGRAMDATA%\Trados\MultiTerm\MultiTerm17\

If that doesn't help we can log a case.  I think the problem could be the ProgramData folder but I'm not 100%. So better to start afresh.

Hi Paul,

This case is 22 days old. You may have missed it, but this procedure has been tried first with no results. An RWS technician worked on it and found it was probably due to a "physical address" issue between Multiterm and NordVPN.

NordVPN has also been contacted — see the details below.

As per NordVPN technician, Multiterm app generally does not work well with VPNs due to a defect in the app which creates a need for the physical address after connecting to a VPN. Nothing has been fixed yet, but I can access Multiterm using an alternative solution.

Alternative Solution provided by RWS technician

- Do not open MultiTerm

- Disable NordVPN for 5 minutes

- Disable Nord Lynx from ncpa.cpl from the Control Panel:

• Windows key + R (Run command)
• Type: ncpa.cpl
• Right-click on NordVPN NordLinx connection icon and select “disable”

- Open Multiterm

- Open the termbase or the termbases

 Case number: CS0027997

Explanations provided by NordVPN:  

Our OpenVPN protocols should provide a physical address. 

That being said, please try switching the connection protocol to either of our OpenVPN protocols. It can be changed in the NordVPN application settings. 

Within the Windows NordVPN application: navigate to Settings and click on the “Connection” tab > locate the “VPN protocol” option > select OpenVPN (TCP or UDP)

(I personally tried this, but it didn’t solve the problem) 

However, we cannot guarantee this works, as the Multiterm app generally does not work well with VPNs due to a defect in their app, which creates a need for the physical address after connecting to a VPN.

 Helene Minville 

Interesting.  I don't see the support cases as I don't have access to them.

But perhaps, based on this you could try something different and use split tunnelling which is something NordVPN supports:

https://support.nordvpn.com/hc/en-us/articles/19618692366865-What-is-Split-Tunneling-and-how-to-use-it?

Split tunnelling lets you exclude MultiTerm from the VPN entirely.

Here are the likely steps:

• Open NordVPN app -> Settings
• Find Split Tunneling (might be under Advanced or Connection)
• Add MultiTerm.exe to the exclusion list
• Done - MultiTerm bypasses VPN, everything else stays protected

Maybe that would help?

 Helene Minville 

Interesting.  I don't see the support cases as I don't have access to them.

But perhaps, based on this you could try something different and use split tunnelling which is something NordVPN supports:

https://support.nordvpn.com/hc/en-us/articles/19618692366865-What-is-Split-Tunneling-and-how-to-use-it?

Split tunnelling lets you exclude MultiTerm from the VPN entirely.

Here are the likely steps:

• Open NordVPN app -> Settings
• Find Split Tunneling (might be under Advanced or Connection)
• Add MultiTerm.exe to the exclusion list
• Done - MultiTerm bypasses VPN, everything else stays protected

Maybe that would help?