• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 4922 views
  • Users 0 members are here
Options

ProjectAutomation API: Sdl.ProjectAutomation.FileBased.LicensingException: License check failed, with exception: Sdl.Core.PluginFramework.PluginFrameworkException: Cannot validate SDL plug-in: Sdl.Common.Licensing.Provider.SafeNetRMS.SafeNetRMSicensingPro

Rieko Matsunaga

Hello,

 

I have a stand-alone application which used to work fine with Studio 2014 and Groupshare 2014.  We are considering moving onto Studio 2017 and Groupshare 2017, but it's facing an error mentioned in the subject.  We are still in the testing phase of 2017, so the licence we have may be different from the one we have for 2014.  Here's some reference to what kind of license we currently use for 2017:

Could the license we are using for testing be related to the error I'm encountering?  What can we do to avoid the error?

On a side note, the app use AssemblyResolver.dll provided by Romulus, and I did rebuild the project which says that it has been modified to work with 2017.

 

Thank you!

Rieko Matsunaga
Rate translation
×
Suggest better translation
×
Parents
  • 0

    This is an open issue at the moment. The workaround is to deploy the application inside Trados Studio installation folder. We have in internal open issue on this - LTB - 1136.

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/

  • 0 in reply to Romulus Crisan (former member)
    I'm wondering what should be the internal issue number good for, given the fact that we have absolutely no idea how low on the list it is and/or how (un)important it is for the product management... especially when we also have absolutely no way to influence these... :-\
  • 0 in reply to Evzen Polenka
    So you can refer to it when future releases come out and then it makes it easier for us to let you know whether it's been fixed or not. Also we refer to them in the release notes I think.

    It's only information for you.

    And of course you can influence them... if enough people ask about it then the priority is always raised. If only one person needs a fix for something then it may never get a high priority.

    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

  • 0 in reply to Paul

    The thing is that

    • I do not remember seeing any such reference in the release notes (i.e. what you think is not what we actually get)
    • normal people refer to issues by their descriptions/symptoms, not by some obscure codes
    • we can see issues reported by many people lying around for YEARS completely ignored (i.e. we obviously do NOT have any REAL influence on their priority)
      for example this very one...

    So in reality it's just useless.
  • 0 in reply to Evzen Polenka

    Unknown said:
    • I do not remember seeing any such reference in the release notes (i.e. what you think is not what we actually get)
    • normal people refer to issues by their descriptions/symptoms, not by some obscure codes

    You're right.  Must just be some internal notes I was thinking of.  But perhaps we should start to do this in addition to the text for normal people.

    Unknown said:
    • we can see issues reported by many people lying around for YEARS completely ignored (i.e. we obviously do NOT have any REAL influence on their priority)
      for example this very one...

    So in reality it's just useless.

    Perhaps you don't.

    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
  • 0 in reply to Evzen Polenka

    Unknown said:
    • I do not remember seeing any such reference in the release notes (i.e. what you think is not what we actually get)
    • normal people refer to issues by their descriptions/symptoms, not by some obscure codes

    You're right.  Must just be some internal notes I was thinking of.  But perhaps we should start to do this in addition to the text for normal people.

    Unknown said:
    • we can see issues reported by many people lying around for YEARS completely ignored (i.e. we obviously do NOT have any REAL influence on their priority)
      for example this very one...

    So in reality it's just useless.

    Perhaps you don't.

    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

Children
No Data