This is a known, longstanding, difficult to debug issue with their licensing provider that seems to affect a small number of users, and unfortunately you are in that category. 
The good news is that, as mentioned by L&L support in the thread I linked to, it seems they’ve made a breakthrough in reproducing the issue, so that’s a very big step toward resolving it.
Best,
Jim