I'd put it differently. The possible problems are:

1. A bug.
2. A bug that you haven't solved for years
3. A bloody bug that should never be there and that compromises project exportability = MAJOR issue

Just ran into the same problem and won't even bother troubleshooting after what I've read on these forums (can't find the specified files anywhere). Will have to recreate and pre-translate the whole project again. This is the second or third time this month. The former cases were related with unexpected Studio crashes.

MemoQ, here I come.

You can create a new project using the sdlxliff file/s set to 'Analyse only'...

That way you don't have to retranslate...

Happy New Year

All the best,

Ali

You can create a new project using the sdlxliff file/s set to 'Analyse only'...

That way you don't have to retranslate...

Happy New Year

All the best,

Ali

I pre-translate the whole project from TM. That way I retrieve the progress. That's what I've been compelled to do with subsequent failures of Studio for years.

Sorry to hear you're always having problems with it...

This only ever happens to me with projects that came from client packages. As most of my work is proofreading, the projects I receive are at the review stage. There is nothing in the accompanying TM as the translated work isn't updated to the TM till I review it. So if I use just the translated sdlxliff file as source, prepare the project using 'Analyse only' then I don't lose the translator's work and the whole thing works fine.

Happy new Year,

Ali

In fact, this particular problem has happened to me for the first time in 7 years of my Studio usage. But there have been other reasons for having to re-create projects, mostly related with Studio crashes without prior saving (the autosaving feature is a bit of a pain in the butt, but I suppose I'll have to enable it after all).

Happy New Year with less Studio faults indeed.

Alison, thanks a lot for the elaborate description. I get occasional crashes in different situations, but they don't seem related to what you've brought up. The last crash, for instance, was after the "object reference not set to blah blah" thing that's been popping up on me since forever. But that's not the only thing, so let's just skip this issue altogether and focus on the OP, as I wouldn't want to be accused of hijacking the thread.

OK, Adrian

In that case, if I had the 'dependencies file' message coming up on projects I'd created myself, I'd run a repair of Studio and MultiTerm.

I do this with any software that is malfunctioning... For example, I ran a repair on Microsoft Office this morning because Excel has been misbehaving... If that doesn't work, I run a reset. It's the logical way to keep your software environment healthy.

Enjoy the rest of your day! I will, I'm proofreading, my Favourite Thing ... or at least I should be heheh 

All the best,

Ali