Error with Floating License

[Aaron]

We are having an error with our floating license. Everything was working fine up until a few days ago, and I’m unaware of any network changes that were made. I confirmed that our LSA did not get moved to a different machine (it’s running on the same VM is has for the past couple of years). The attached document walks you through the issue. There error message I do see on the ‘Current License’ context window is ‘Invalid character in Base-64 string.’

[eadocX Support]

Please can you create another Licence Server Application from the website at
http://keygen.eadocx.com/UsdLicenseService/ecommerce/generatelsa.aspx

We have just upgraded the LSA to fix this issue, so we beleive this version should fix the ‘base 64’ problem.
Thanks

• This reply was modified 8 years, 7 months ago by eadocX Support.

[André Wittwer]

We have the same error message as you described here. Was is it helpful to reinstall the LSA?

Thanks for your answer in advance!

[eadocX Support]

No news is usually good news!
If you have this ‘base 64’ problem, the only advice we have is to create a new LSA from the latest code. There are no other solutions.

[André Wittwer]

To install the latest LSA tool was helpful. Thanks for your reply.

[Seidel Theresa]

Hi,

i’ve got the same problem. But creating a new LSA did not solve it. I still get “Invalid character in a Base-64 string”.
Is there any other way?

[Jarrod Moffitt]

We are having the same issue , it started about 4 days ago. Currently it looks like the website to generate the LSA is down so I am not able to see if the new install resolves this issue.

This floating license method has been working for us for for some time (like a year or two) so I dont understand why it would just stop working unless a Microsoft Patch or similar had broken the engine.

[eadocX Support]

Update 10th October 2016: Our service provider has had a hardware failure, so the LSA generator is currently not available. We’re really sorry about this and you won’t be surprised that we are encouraging them to fix this.
With a big stick.

The underlying problem is caused by when Microsoft apply maintenance to the operating system. Wec cannot identify which change to which OS component.
Creating a new LSA – from a newer version of the LSA code – fixes the problem MOST of the time, but not 100%. If is still doesn’t work, then we will replace your floating licences with either:
– fixed ones, on the basis of 1 floating = 4 fixed
– an company-wide licence, so all users share a singe key. Ask us about this.

[Jarrod Moffitt]

Thanks for the update, seeing that the LSA is down can you supply us with the company wide license or is this at an extra cost ? If so please supply me with the 4 fixed licenses so that we can get our users up and running again.

[Author]

Posts