Hello Adrian Pop ,

I would first update both your Studio and your MultiTerm versions to the latest stand (Help- Check for updates).

Next i would suggest a repair/reset as follows

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039395

If the problem persists, please check where the TB's are saved (locally or in the cloud). If they are stored in the cloud, try saving them locally to see if this resolves the issue.

It is also perhaps worth also recreating the Project Template, ensuring only the resources are added as required.

Hi Steven,

Thank you for providing the default troubleshooting answer and trying to first make sure that the problem is not caused by installation/versioning problems.

I am able to reproduce this behavior with Studio 2021 as well and my feeling is that this is somehow a limitation(?) related to how Studio uses MultiTerm via OLE Automation behind the scenes.

I have prepared a zip with 3 very basic projects and 65 dummy termbases which can be used to reproduce the problem:

https://www.dropbox.com/s/v754zgjo4fpxx3m/64TermBasesLimit.zip?dl=1

Could you please give it a try to see if the problem is reproductible on your side?

If yes, please unzip the files together with the 64TermBasesLimit folder into your C:\Temp  so you will have something like below:

Preserving the paths is important because inside the projects the termbases are referred via absolute paths.

Now please do the following:

Part1

Open Studio

Open Project1 - open the file in the editor - close and remove Project1 from the list

Open Project2 - open the file in the editor - close and remove Project2 from the list

Open Project3 - open the file in the editor => you should get a TB error and in the logs the famous "multimedia object" error

Part2

Close Studio

Open Studio again

Open Project3 - open the file in the editor => no error - the TB works just fine. 

If in Part1, after opening/closing Project1 and Project2, instead of Project3  you open any of your projects which has at least one TB attached you will also get the error and, in my opinion, this more or less proves the hypothesis that 64 is a hard limit somewhere.

I would be very glad if you would try to reproduce the problem on your side and in case it is reproductible to also ask the DEV team about it.

Thanks,

Adrian

Hi Adrian Pop ,

Thanks for the files,

We have been able to replicate this in 2019/2021, and I have passed this on to our support team (Case 00606788).

Once the technical team have investigated this further, I will update you.

Hi Adrian Pop ,

Thanks for the files,

We have been able to replicate this in 2019/2021, and I have passed this on to our support team (Case 00606788).

Once the technical team have investigated this further, I will update you.

Thank you very much Steven! Greatly appreciated!

Would it be possible to make the case also accessible for our organization (CdT)?

Regards,

Adrian

Hello Adrian Pop

Our internal systems are not available outside of our organization.

I will however keep you informed on the progress.

Hi any news about this issue?

Thanks,

Adrian

Hello Adrian Pop ,

Apologies for not updating earlier.

The support team have tried to replicate this and have been unsuccessful- even when using 120 TermBases across multiple projects.

It would be good if other users contributed to this thread if they have similar issues as then we might be able to see a pattern (and something we may have missed in testing).

Thanks for the quick answer Steven!

I have to say that I am somewhat surprised by the support team's response given that you already confirmed that, using my sample project, you were able to replicate my issue in both Studio 2019 and 2021.

Is there any way I can continue this discussion directly with them? Should I submit this again directly via our support contract? 

Regards,

Adrian