Marcos Janariz Ripalda Support Case Id : 00635603. Support case has been logged for your assistance. Please check your SDL Community email address for updates.

Marcos Janariz Ripalda said:

Paul, could you please explain whether this limit for the number of resets exists?

Yes it does.  The support team will reset for you, but if you do this all the time it may raise questions over why you need so many.

Hi Paul, thank you for your answer.

The reason is quite simple. I have 2 Trados Studio 2019 licenses. If you have the means to check this, you will see that I use most of the time one. However, I work from four places where I have the possibility to work from: Barcelona, Francfort, Noain (close to Pamplona in Northern Spain) and another city where my mother-in-law lives. But when COVID is away, I intend to travel to other countries within Europe and I always take my laptop with me. That means that every time that I move I will have this issues 2 per journey. It means, if I move a total of 12 times a year, I will have to process 24 license resets a year. While I have no problem to do so, even though I have to wait 30 minutes each time, this could be a problem at your side, even though you can easily my machine-ID. I bought the computer that will replace the one that I am using now five months ago. However, I have no time to move some software from this computer to the new one. Since I have two licenses for SDL Trados Studio, I have already installed the other license in my new computer, but I intend to leave the license that I am using now in this computer where it is and will use for travelling. I am now realising that if I travel to different cities within one country that is going to be a lot of work for both of us. I understand that you combat fraud licenses, but isn't there any other way to identify the computer where a license is installed such that this does not occur?

Best regards and thanks for your help.

J.M. Janariz

Marcos Janariz Ripalda

It is probably not possible to change this as it's a security aspect of the licence. But you may be able to work around this in a couple of ways.  First of all, deactivate your licence before you use the USB stick.  Then reactivate once the USB is in place.  Similarly, deactivate before removing it and reactivate again afterwards.  That's probably the most appropriate solution in your case.

Another option that "might" work... but it may also have a similar problem... would be to use the offline activation certificate:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039784

Although I think this may be subject to the same restriction.  David Watson might have some idea here as he knows a lot more about the technical workings of the licensing system than I do.

Marcos Janariz Ripalda said:

isn't there any other way to identify the computer where a license is installed such that this does not occur?

I would note that this isn't a licensing system we have developed, so this isn't something we can simply try to find a way to work around this.  It would also defeat the object of the system in the first place if it was so easy.

Marcos Janariz Ripalda

It is probably not possible to change this as it's a security aspect of the licence. But you may be able to work around this in a couple of ways.  First of all, deactivate your licence before you use the USB stick.  Then reactivate once the USB is in place.  Similarly, deactivate before removing it and reactivate again afterwards.  That's probably the most appropriate solution in your case.

Another option that "might" work... but it may also have a similar problem... would be to use the offline activation certificate:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039784

Although I think this may be subject to the same restriction.  David Watson might have some idea here as he knows a lot more about the technical workings of the licensing system than I do.

Marcos Janariz Ripalda said:

isn't there any other way to identify the computer where a license is installed such that this does not occur?

I would note that this isn't a licensing system we have developed, so this isn't something we can simply try to find a way to work around this.  It would also defeat the object of the system in the first place if it was so easy.

Thank you Paul for your quick answer. I will try the first method. Should it not work, I will try the second one. 

Now I remember that as long as I do not move to a foreign country, the Licensing System does not generate the error. Mos probably this happens only when moving to a foreign country because I am using a USB LTE stick. However, the next time that I connect through a WLAN router, I will see whether the same error happens.

Best regards,

JMJR