Hello Manuel,

I'm sorry to hear about the issue you're experiencing with QuickPlace. Based on your description, it seems like the issue might be related to the settings of your translation memory. Here's a step-by-step guide on how to check and adjust these settings:

Step 1: Open Trados Studio.

Step 2: Go to the "Project Settings" menu.

Step 3: Navigate to "Language Pairs > All Language Pairs > Translation Memory and Automated Translation".

Step 4: Check if your file-based or server-based translation memory is listed first. If it's not, adjust the order to make sure it is.

If the issue persists after following these steps, it might be a more complex problem that requires a deeper investigation. In such a case, I would recommend creating a backup of your settings and then resetting them to the default.

Remember, it's always a good idea to keep your software up to date. Check for updates within the application regularly to ensure you have the latest features and bug fixes.

I hope this helps! If you have any other questions, feel free to ask.

Best regards,

RWS Community AI

I am afraid this answer does not work. I did not mention it, but I had seen this "solution" before (https://gateway.sdl.com/apex/communityknowledge?articleName=000019392), but my server-based TM was already on top of the list. I already tried disabling or removing the Cloud resource, but it still does not work.

For the second part of this reply, I already said I had restored Trados to default settings...

Also, I am currently using Trados Studio 2022 SR2 - 17.2.9.18688, which AFAIK, is the latest version, so updating won't fix this issue either, I am afraid .

What else can I do?

Kind regards,

Manuel

Manuel Rubio Máñez 

Have you checked that your shortcut is still active in the keyboard shortcut options?  Probably a silly question but might be worth checking.

Hi Paul,

Thank you for your answer and sorry for the late answer. I have been working without Trados during the last fortnight and did not see the notification.

Yes, I checked and tried to change it to see if it worked with another shortcut, but to no avail.

Luckily enough, it seems that this was a one-time problem that only happened with that specific package/project from client, so I guess (and hope!) it was just a temporary glitch. As a matter of fact, I am now working with another project and it works normally. I will pay more attention next time I receive the aforementioned "Index out of place" error so that I can provide further details.

I guess this thread can be closed.

Kind regards,

Manuel