Paul,

The language pair is Swedish-English, and the operating system is Windows 10 (installed in English).

Kind regards,
Johanna

Hello Paul, I think this is what's happening to me too.

I am translating from FR-FR to EN-UK.

I have a variety of error messages.

It's a new project I created today (since SR2 was installed). For example, I just clicked on the 'Termbases' icon in the Term Recognition window, and got the error 'Value cannot be null. Parameter name: key'. If I try to access termbase settings via the 'Project Settings' tab on the 'Home' ribbon I get 'Failed to create setting page'.

This is after I tried to add TBs and had error messages, including a red cross through the window where TBs are listed, when I did manage to access the project settings after I set up the project. The TBs are stored on a local external hard drive, and I was able to access them there before.

Incidentally, I updated Multiterm as well and can open and search my TBs in Multiterm, I tried.

Thanks in advance for any pointers,

Kim

Hello Paul, I think this is what's happening to me too.

I am translating from FR-FR to EN-UK.

I have a variety of error messages.

It's a new project I created today (since SR2 was installed). For example, I just clicked on the 'Termbases' icon in the Term Recognition window, and got the error 'Value cannot be null. Parameter name: key'. If I try to access termbase settings via the 'Project Settings' tab on the 'Home' ribbon I get 'Failed to create setting page'.

This is after I tried to add TBs and had error messages, including a red cross through the window where TBs are listed, when I did manage to access the project settings after I set up the project. The TBs are stored on a local external hard drive, and I was able to access them there before.

Incidentally, I updated Multiterm as well and can open and search my TBs in Multiterm, I tried.

Thanks in advance for any pointers,

Kim

Hi Kim,

Thanks for bringing this over to the community... easier to discuss these things in here!  The problem seems to be related to the location of the TBs and we are working on a number of fixes (this one included) at the moment.  It only affects SR2.  So if you can move your TBs to your local drive and not the external local one, then it should work.

You might also find this solution useful too:

Unknown said:

You should be able to access the mapped drive letters in the Open File-based Termbase dialog. and if not you should at least be able to enter the file path directly into the File name field, for example "X:\Termbases\mytermbase.sdltb" and press Enter. On the other hand this could possibly be down to the operating system so perhaps it does not work for you. 

Yes, as far as I can tell this is only a problem in this new update and the mapped drive has been proven to work in at least one instance where it did not work with the unc path in SR2.

Regards

Paul