We installed a security hotfix on all our VM instances. BAM all DB licenses are inactive, now we have to create new keys for all of them.
We sometimes have to create new keys if we update to a newer objectdb version.
We had to create new keys multiple times because of the unstable activation issues.
We sometimes have to create new keys and we don't know even why.
The manual creation of license keys for a site license is not ideal to say the least. There has to be a better way!
Only changing MAC addresses should require re-activation, so it is likely that the security hotfix that you installed changed the MAC address somehow. Examining the MAC addresses in your new activations today confirm that these are new MAC addresses.
Past activation stability issues have been fixed in version 2.9.3 and there are no new known issues. If you create a new activation using version 2.9.3 or later and still have issues (except when the MAC addresses of your device change) please provide more details.
We have a site license and we have to create new keys for the DB for the mentioned reasons and for every new VM, every new PC/Laptop.
It is really tiresome. As we bought the license years ago there was hinted at a automatic activation that never got implemented. This is the only product we know of with this kind of security and it's a real bother.
We understand that depending on the license type some checks are necessary but for a site license to have to do this is not practical.
Activation is a simple procedure that depends on the MAC address of the device. This used to be fixed in the past . However, we do not have control on the MAC address, and changes in recent years made this less stable, first on Mac computers, then on VMs and Dockers. According to your private support ticket you are using an old 5-year version of ObjectDB. Newer versions (starting 2.9.3) are much better and it is highly recommended to upgrade (also due to many other reasons). We are working on further improvements and will try to work on an immediate workaround with you in the private support ticket.
Sorry my bad, i meant we use 2.9.3 not 2.8.3. We alsways try to use the newest version.
I fixed it in the other ticket.
No problem. Please see the reply in your private support ticket.