Hello,

I read several entries with similar titles, but about previous versions of Studio. For general use, I'm noting answers I found that didn't work for me, and finally what I did today (2025-03-05) that worked for me… today. I intend to update.

I found this solution here, https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/50239/terminology-database-file-not-found-after-update/162537
It should be noted that this was for a slightly different problem, i.e. termbases not being found, as opposed to termbases showing no results.
Thanks to David Earnshaw and Judith Marker, though I use Judith's solution, which is slightly different from David's, i.e. not using One Drive.

I totally agree with Judith who wrote this:
“After spending some hours with this issue, too, I have copied my termbases from the Mac side to the PC side in Parallels. Now it works. I can confirm all issues described above and also that locating the termbases on the Mac side (despite the // at the beginning of the path) worked in the past. This is obviously a bug; someone has forgotten about flexible paths and created paths for Windows systems only. I hope this will be fixed SOON.”
(Her hope did not materialize, as this was written about Studio 2022.)

TL:DR: That's the solution that seemed to work for me: storing termbases on the Windows hard disk, on the first level.

--

I'm using Studio 2024 with Parallels Desktop 20 on a Mac with the M2 chip. I've always used Studio with Parallels, I have been using my Mac with the M2 chip for over a year, and never consistently had that problem before. The problem might show up, but I usually corrected it by recreating the project from scratch, and then I'd be able to see results in the database window the usual way.

At this point, the problem is consistent, whatever the project or database. 

I found that most answers to the question about previous versions of Studio included this series of steps:

Step 1: Ensure that both Trados Studio and MultiTerm are updated to the latest version. You can check for updates within the application.

I did that. I did the same with my version of Windows and of Parallels. All my applications are using the most recent versions.

Step 2: Try to restart both applications. Sometimes, a simple restart can resolve minor issues.

I did that, by restarting Windows from Parallels, then by restarting Parallels from the Mac, then by restarting the Mac altogether. It didn't help.

Step 3: Check if the termbase is correctly linked to your project. You can do this by going to the 'Project Settings' and then to the 'Language Pairs' and 'All Language Pairs' tabs. Under 'Terminology', you should see your termbase. If it's not there, you can add it.

I did that. For good measure, I started a new project and most carefully followed the usual steps. It didn't help.

Step 4: If the problem persists, you might need to repair your installation of Trados Studio and MultiTerm. You can do this from the 'Programs and Features' section of your computer's Control Panel. Find Trados Studio and MultiTerm in the list, right-click on each one, and select 'Repair'.

I did that. It didn't help.

Step 5: If none of the above steps work, you might need to recreate your termbase. Please ensure you have a backup of your data before doing this.

I did that. It didn't help.

Other things I did, searching questions:

Checking that the path to the file is easy and that no names include special characters.

I did that. It should be noted that those haven't been changed since the time things worked. Anyway… you guessed it… it didn't help.

Sometimes it can be a corrupted entry in a file-based TB that does it. Occasionally, I had to export and import the TB into a new Termbase for it to work.

I did the whole export and repair and businesses from the latest version of Multiterm. Plus, it happens with all my databases, including database that weren't edited recently and that used to work correctly.

Maybe this is due to you keeping the termbase in OneDrive and it's set to be stored in the cloud? 

My databases are not stored in the cloud, they're stored on my computer's hard disk, the way they've always been. There hasn't been any change in this situation, so I don't think this has anything to do with the problem.

Check that the path to the file doesn't include double backslashes.

This was the path to the file, as provided by the Windows menu.

Z:\Documents\Docs Windows\Termbases\EMSFC.sdltb

I wasn't able to check the path to Z.

--

Note to self: searching the community is helpful.

Hélène Dion
Communication Cinq sur cinq