TM not opening in Studio 2017 after SR update

Uninstalled and reinstalled SDL Studio 2017. Created new TMs. Deleted previous TMs. Reset profile to VAL 0 as advised by a website. Tried as administrator. No positive result and still unable to open a TM for my file. Original error message was XXX.sdltm could not be opened and has been disabled. Has anybody found the solution ? Thanks.

Parents
  • Unknown said:

    Uninstalled and reinstalled SDL Studio 2017. Created new TMs. Deleted previous TMs. Reset profile to VAL 0 as advised by a website. Tried as administrator. No positive result and still unable to open a TM for my file. Original error message was XXX.sdltm could not be opened and has been disabled. Has anybody found the solution ? Thanks.

     

    Hi Patrick,

    Have you by any chance moved/deleted the TM that can't be opened? The reason I ask is because I just had this message appear after opening a project that had an AnyTM attached to it which I had moved to a different folder last week. Since Studio can't find the TM, I get the message below:

     

     

    The description of your problem mentions that you have created new TMs, so I didn't think this could be the cause, but it may be worth exploring. Are you creating and deleting TMs from your Project Settings window or from the Translation Memories view?

  • Hi , you were spot on. I spoke to Vlad in support and he confirmed that the issues were two-fold:

    1. Moving TMs around outside of Studio so Studio didn't know where they were anymore, and
    2. Some general lack of understanding about how Studio works. Just needs a bit more experience after using T2007 for a long time

    There was nothing related to SR1 at all.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply Children
  • This could have been sorted out easily here. There are only few things necessary to know - and having the necessary information we would have been able to point the asker to the right solution.
    This again shows how important it is to help others to help you. If someone seeks help, it is a very good advice to describe the problem as precise as possible. Maybe you could insert a sort of a "prepost" in each empty field, when someone starts a topic here. There you could list all the necessary info we need here. Like product version, error message, steps taken and so on.
    Chaotic posting, not reacting to valid questions, giving stodgy answers and ranting all around the place are certainly not valid ways to get help. I admire you for all the patience you have, Paul. As you can certainly read in my answers, I have left this patience way behind me - and I do not regret there. Asker who cannot even answer a simple question from people willing to help do not deserve any help at all.

    Best regards, Jerzy

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • I think it would also be a good idea if community users could state their level of expertise or maybe how long they've been using the program. That way those who are available/willing to help could gauge whether it's a simple or complex matter. I still remember some of the questions I had when I first started using Studio and many of them had simple answers, but sometimes I didn't even know how to ask, not being familiar with how the program worked.

    In this particular case, I actually thought of this yesterday, TM having been moved to a different location, but it seemed too simple/obvious an answer given the various steps listed by the user already. If I had known that he had recently migrated from T2007, I wouldn't have hesitated to bring it up.