Activation fails on version 2.9.5_01

#1

Hi, 2.9.5_01 is rejecting our activation key, and running Activator in 2.9.5_01 to get a new key gives us keys that still don't work. Tried Activator separately on my work Macbook and a Linux server, both keys got rejected on the respective machines. We have a Site license that should cover all 2.x releases. Generating a new activation key from the version we currently use (2.8.9.b04) on my work Macbook works.

I'm obviously not going to post our activation credentials or keys on a public forum, so please advise what to do next.

#2

We haven't encountered this issue in recent versions. Before investigating further, please double-check that the ObjectDB configuration file containing your activation key is actually being used. The most common reason for activation failures after an upgrade is that the new version was installed in a different directory and is ignoring the old configuration file. To test this, try intentionally adding invalid XML to the configuration file. If the application runs without throwing an XML parsing error, it means ObjectDB is not reading that file.

ObjectDB Support
#3

I stepped through the code that validates the activation key, and both keys are being rejected at different points of the check, so there is definitely something wrong with the key generator or the key check. I don't want to disclose details in a public forum, but if there is a private contact I can send the Site license credentials, the generated keys, and where exactly the activation check is failing.

#4

Yes, create a new private support ticket.

ObjectDB Support

Reply