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? 

Hi Steven:

2 clients, 1 using Trados 2019 and the other using 2017. I think it happened the first time after receiving a package from the client using the 2019 version. Yes, the packages are ppx packages.

Screen shots:

Firs the initial error:

After accepting, everything is normal:

After select "Close" above, the second error message:

Hi Steven:

It's happened with 2 clients. One is using 2019 (just updated recently) and the other using the 2017 version. I think the problem first occurred on 22 October after receiving a package from the client using the 2019 version. Yes, the packages are ppx packages. I save the packages where I always do, separated by client, month, project and in a separate "studio" folder. No change.

Screen shots:

First error message after selecting "open package":

After selecting "Ok" above, everything is normal:

After selecting "Close" above, the second error appears:

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.

Hi Steven. Thanks for your reply, but I really don't understand what you want me to do. I'm not a computer expert. The process has always been very simple and straight-forward, and now all of a sudden there is a change. The path is already short: d\2019\client\month\project\studio. And then package in that "studio" folder opens up 5 other folders, one of which should be the "Tm" folder, which is not appearing.

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.

Hi Steven,

Like I said, the path is short (d\2019\client\month\project\studio), which is shorter than the one you suggest (C:\Users\USER\Documents\Studio 2019\Projects\Client XYZ). The error message is showing some strange path going who knows where regarding the translation memory only, but where I am saving my packages is actually the location shown on the right-hand side of the Trados "Projects" screen (on your screen shot (C:\Users\swhale...), right? If you want to call, great. I'm reluctant to give someone I don't know control over my computer. Do you work at SDL? In any event, I haven't changed anything that I've been doing since I've had Trados 2017, and everything has been working fine up to now. Has SDL changed something? My clients say that they haven't done anything different, except for the one client upgrading to Trados 2019.

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.

Hi Steven:

I did as you suggested and found that, indeed, the path to the tm folder was very long. I copied the "tm" folder and pasted it in the usual "studio" folder, then specified Trados that it should search for the "tm" folder in this  location, and it opened it properly and everything worked.

However, the main problem persists. When I usually open a package, Trados automatically creates the "Tm" folder in my "studio" folder, which has a very short path. But now, when I open the package the "tm" folder is automatically placed somewhere completely different, in that long and convoluted location that we talked about.

So although I can copy the wrongly placed "tm" folder, paste it in the correct "studio" folder and start working properly again, the program is always initially misplacing the "tm" folder. I would like to know why this could be happening, and if there is a way for me to solve the problem so that when I open up my packages, the "tm" folder gets placed in the proper "studio" folder with everything else, as it always did.

This is the location where Trados is misplacing the "Tm" folder. Usually Trados would place it in my "studio" folder

I would like to talk about this to see if we can re-establish the normal configuration. I'll send you an e-mail.

Thanks,

Scott

Scott McPherson

Hi, I've been having the exact same issue for the last couple of months and wondering if you ever found a solution. Thanks.