Sotir Rangelov 

Can you share the full path please?

\\192.168.1.91\filestorage\Protemos-projects\erider\TB

Sotir Rangelov 

Thank you.  I think the first thing to do is check your network permissions and Access.  Make sure that the network permissions for the RAID 1 disk and the shared folder are correctly set up.  Sometimes, permissions can get reset or even not get properly configured when moving folders to new locations or disks.

Might also be worth looking at your network path format.  I guess it worked before but could be worth making sure that the network path is correctly formatted.  Maybe try different formats, like using the full network path (\\server\share\folder) or mapping the network drive to a drive letter and accessing it that way.  I'm not aware of any changes here in this update but worth looking if a different format could help.

I'll also check with dev to see if anything could have changed.

Sotir Rangelov 

Thank you.  I think the first thing to do is check your network permissions and Access.  Make sure that the network permissions for the RAID 1 disk and the shared folder are correctly set up.  Sometimes, permissions can get reset or even not get properly configured when moving folders to new locations or disks.

Might also be worth looking at your network path format.  I guess it worked before but could be worth making sure that the network path is correctly formatted.  Maybe try different formats, like using the full network path (\\server\share\folder) or mapping the network drive to a drive letter and accessing it that way.  I'm not aware of any changes here in this update but worth looking if a different format could help.

I'll also check with dev to see if anything could have changed.

Hi!

We just realized in the office that the TMs are working OK and this issue is only with the TBs. I.e. we can add the TMs from the same shared folder. So it should not be an issue with the settings of the RAID1 disk or the shared folder as both Tms and the TBs are on equal basis.

We also noticed that the Multiterm is not updated and this might be the case. We are not able to restart the PC during the working day, so I will post after the EOB.

Sotir

Paul 

We updated the Multiterm to SR2 17.2.2.2737. Multiterm can open the TB and can edit it. But when I try to add the same TB to a project settings through Trados Studio - it cannot open it (the same error).

Sotir Rangelov 

Did you look at these things?

Paul said:

Maybe try different formats, like using the full network path (\\server\share\folder) or mapping the network drive to a drive letter and accessing it that way.

The advice I also got from the dev team after speaking to them was that mapping the network to a drive may be the solution here.

 Sotir Rangelov 

Can you also provide a stack trace for this error if you have one?  So the full details of your error message.

 Andrei Caia fyi.

Andrei Caia 

This is the only thing that I see:

I do not know how to do this, so I will try to search on the internet and will let you know.