Carmen Vollmuth 

Did you try the knowledgebase?

https://gateway.sdl.com/apex/communityknowledge?articleName=000009276

Carmen Vollmuth 

In fact I can see you probably did as the steps you outline are similar.

What happens if you put a copy of this TM on your local machine and not on a network drive at all?  Trados Studio, for single users, is designed to use files on the local machine and problems can occur when you put them on a network drive.  For example, performance issues, compatibility problems, file locking conflicts, security concerns, data loss or corruption, network reliability challenges, version control difficulties, increased backup and recovery needs, and increased IT support demands.

Carmen Vollmuth 

In fact I can see you probably did as the steps you outline are similar.

What happens if you put a copy of this TM on your local machine and not on a network drive at all?  Trados Studio, for single users, is designed to use files on the local machine and problems can occur when you put them on a network drive.  For example, performance issues, compatibility problems, file locking conflicts, security concerns, data loss or corruption, network reliability challenges, version control difficulties, increased backup and recovery needs, and increased IT support demands.

Working on the local machine is not in line with our corporate guidelines. Though it is, what I usually do, it is part of the current problem: the TM on the network that was supposed to be the backup is corrupt and the local data was lost as a result of the anti-virus measures.

I am aware of the problems you list, but wouldn't rather RWS need to develop a tool that works smoothlessly in a network environment? 

But anyway, this does not solve my problem...

Any other ideas?

I forgot: I did all of the described with the TM on the local drive.

Carmen Vollmuth 

Carmen Vollmuth said:

I forgot: I did all of the described with the TM on the local drive.

And you still have this problem?

Carmen Vollmuth said:

the TM on the network that was supposed to be the backup is corrupt

Are you sure the one you have now isn't corrupt?  Have you attempted to repair it?

Is it possible for us to have a copy of your TM?

Carmen Vollmuth 

Carmen Vollmuth said:

Working on the local machine is not in line with our corporate guidelines.

So this would not be our problem then?

Carmen Vollmuth said:

I am aware of the problems you list, but wouldn't rather RWS need to develop a tool that works smoothlessly in a network environment? 

We have done... it's called Language Cloud.  You could use this, especially if the TM is for your own use.  Trying to use a file-based TM in the way you are is a risk, but it's one you don't have to take.

Thanks for answering.

Yes, the issue persists.
I am not sure, the TM is corrupt, but Studio would not use it, so it is as much as useless.
It is a fairly large TM, has been nursed for some 15 years or so. The repair tool might simply buckle under its weight... 

I could provide you with a copy of it (in fact, I'd hoped someone would offer to look into it).

Meanwhile, enjoy the weekend.

Yes the cloud... It's true, and I specially attended a webinar. However, there are quite a few handy features not yet availble. An then of course again: some - albeit - outdated guidelines... There are no easy solutions.

Carmen Vollmuth 

Carmen Vollmuth said:

I could provide you with a copy of it (in fact, I'd hoped someone would offer to look into it).

ok - send me a link so I can download it - pfilkin at sdl dotcom.

All-clear signal

The TM repair process seemed to stall. But after aborting it I realized, that the Repair file had a certain data volume. And it would grow with the time the process was running. So on Friday night after working hours I launched the process and let it sit. And it did complete after 2 hours.