Hello Leonardo Alvarez ,

It would be good to know if you were previously using the Beta version (available in 2017- but removed in the 2019 version).

The BETA version allowed you to use a number of TB's- whereas these are now limited (depending on your package you are subscribing to) in 2019 (could be the cause of the error message).

Therefore, it may be necessary to update your subscription options.

If the problem persists, please log a support ticket.

Hello Leonardo Alvarez ,

It would be good to know if you were previously using the Beta version (available in 2017- but removed in the 2019 version).

The BETA version allowed you to use a number of TB's- whereas these are now limited (depending on your package you are subscribing to) in 2019 (could be the cause of the error message).

Therefore, it may be necessary to update your subscription options.

If the problem persists, please log a support ticket.

Dear Steven, 

I am now able to access my own termbases, so the problem is fixed. 
The problem was that the "SDL Cloud Terminology" was enabled, but I believe it does not support my language pairs (Jap-Esp), so I disabled it and that did it. 

Before the update it was enable but not functioning anyways, but now it was not letting me log in.

In any case, I am able to use my own termbases as before. 

Best regards, 

Leonardo