Hello Peter Höber ,

Can you please see if the resolution from the below article can help you?
gateway.sdl.com/.../communityknowledge

Hello Ana-Maria Matefi 

Thanks for your answer. I've read these posts also, but none of them helps with my problem.

Hopefully there is another solution.

Have a great day

Best regards

Peter

Hi Paul 

Thanks for your answer. I'd like to add, that for some of our projects we use Dropbox to share translation memory files.

I assume for any reason sometimes a translation memory file gets corrupt. Our users were unfortunately not very aware of those warnings while finalizing a batch task with updating the main translation memory. Therefore these warnings may signal for us, that a translation memory file becomes corrupt.

Can you tell us which version of Studio you are using? Peter: Trados Studio 2017

Are you actually using GroupShare as well and if you are which version of GroupShare are you using? Peter: Yes, Version 2017 CU 7. But the problem I mentioned happens with a file based translation memory not with GroupShare.

Does this happen with all projects for the same translation memory? Peter: Yes, with the specific TM-File.

Have you tried repairing your translation memory to see if this is the problem? Peter: Yes, I've tried that and it didn't help. I also opened it with SQLite DB Browser and checked the database there. It says that is is corrupt. 

Have you tried creating a new translation memory and updating into that one?  Peter: Doesn't work unfortunately

Perhaps the issue isn't related to the translation memory at all? Peter: Since the tm-db is corrupt, I think it has definitely something to do with that.

Best regards

Peter

Hi Paul 

Thanks for that. I will discuss it regarding GroupShare internally.

But in terms of my original question: is there a possibility to handle these warnings as errors or give a more noticeable sign?

Best regards
Peter