Trados 2017 errors when receiving packages from clients. Two errors: 1) "Package Repair" 2) "translation memory could not be found". Projects open, but there is no TM.

Question

Just started receiving a couple errors last week when opening some packages sent by clients (I'm working with Trados Studio 2017). The first error is "Package Repair. We found problems with some of the file names in this package and we will attempt to fix them. We recommend that you verify the filenames after the import is done". The next error comes up after the import. It says (translated from Spanish): "The translation memory 'C:..... (big long string)' could not be found. Click on OK to specify the location or on Cancel to deactivate this translation memory". So in other words, Studio cannot find the memory. Looking in my "studio" folder (where I store my projects), the "Tm" folder is missing, as if Trados were not opening it up from the delivered package. My clients state that they are setting up the package as usual. The project opens up as normal in Studio, but there is no translation memory. Very frustrating.

Lydia Simplicio · Accepted Answer

Hello Scott McPherson , 
 It would be helpful if you could post the full error stack please- 
 
 Also posting screen shots are often helpful in identifying the issue. 
 Please also let us where you have saved the package? Is this also a PPX package? 
 Do you know which version of Studio your clients are using?

Lydia Simplicio · Answer

Hello Scott McPherson , 
 What I think is happening is that the path (to the folder) is becoming too long and convoluted. 
 (Windows imposes a maximal length). 
 To test this theory (and hopefully resolve the problem) Im asking you to change the destination/path as per my previous reply- 
 For example - saving the package on your local drive - (the path in your last screen shot is actually very long) 
 C:\Users\USER\Documents\Studio 2019\Projects\Client XYZ 
 Now once you have the package open- you can add other resources as you require. 
 If you want, Im happy to set up a remote session to guide you through this if you prefer. 
 At least then we can rule out the path length as a possible issue.

Lydia Simplicio · Answer

Hi Scott McPherson , 
 I fully understand no one would want to give remote access to someone you dont know. 
 You can always check who you are talking to by hovering over the persons name- 
 When you see the green SDL Logo- you are assured this is one of the team- my direct email is swhale@sdl.com

The paths that you have explained are actually fairly long once you break them down in to their 'steps' 
 Scott McPherson said: (d\2019\client\month\project\studio), 
 the potential length is actually quite long! 
 For Instance Client folder will contain multiple clients- First select the client 
 once you select the client.... you have potentially multiple years and months to choose from... 
 once selected, you now move on to the project.... and so on... 
 As you can see, this can easily exceed the character length Windows allows. 
 Of course I am not denying that you have worked for possibly years this way with out any issues - 
 But computers being what they are, they will eventually max out and need 'cleaning'. Just one extra project could top the limit and cause the issues you are now facing. 
 Im more than happy to give you a call on this (if you provide your number per direct email and you can let me know when its best to call you.

Lydia Simplicio · Answer

Hello Scott McPherson , 
 The screen shots are hard to read- but it appears you have a number of special characters in the URL such as & and %. and that the length of the path is too long. (I think that Windows adds & when the path is too long- which Studio then struggles with) 
 Can you remove the project from Studio please- Then create a new folder - maybe use the default folder (for testing this) - something like 
 C:\Users\USER\Documents\Studio 2019\Projects\Client XYZ 
 Now save the PPX to the new client folder. ensuring the path is as short as possible. 
 Reopen Studio and now open the package as follows- 
 
 This should resolve the issue (hopefully) if im right about the path length.

Trados Studio > 1. Trados Studio

Trados 2017 errors when receiving packages from clients. Two errors: 1) "Package Repair" 2) "translation memory could not be found". Projects open, but there is no TM.

Top Replies