LicenseHttpsErr_InvalidTrustedStorage

[gustavo.loureiro]

Hi,

We've renewed a V20 32 PRO license, which the portal shows is ok.

However, in our local pbx server, the license information on the dashboard still shows the old expiration date, and when I try to update the license information, it returns

LicenseHttpsErr_InvalidTrustedStorage

pbx version is 20.0 Update 3 (Build 659 Alpha)

What is going on?

 

[Evolute IT]

You didn't update in time. Backup, reinstall using latest installer.

U4 is required for activation.

 

[bitn2]

Sometime update still works without reinstall, try this first. Anyway, you need to monitor your pbx for updates or do automatic updates to avoid this problems.

 

[gustavo.loureiro]

Sometime update still works without reinstall, try this first. Anyway, you need to monitor your pbx for updates or do automatic updates to avoid this problems.

I was going to ask that.

The risk is breaking things, since I'll skip release Build 20.0.3.762 that could have changed the database, correct?

(in the dashboard, current version is Build 20.0.3.659 and the new update version is Build 20.0.3.806)

As for reinstalling and then uploading the backup, isn't the risk the same?

 

[SteveITS]

A restore can import older versions of the database.

Once a year or so, 3CX has an update that is required to maintain activation.

 

[gustavo.loureiro]

So, in this specific case where I have Build 20.0.3.659 and the system made available Build 20.0.3.762 to update, do you think it's safe to update, instead of reinstalling?

 

[SteveITS]

3.659 was an Alpha release, 3.762 is the Beta. Normally you'd progress from Alpha to Beta to RC to final, which are all manual updates. Though one should be only on released versions on a production server...that might be part of the problem here. Automatic updates will only install release versions.

You can try it and see. Worst case you need to install new and restore from a backup, which is where you are now.

 

[gustavo.loureiro]

3.659 was an Alpha release, 3.762 is the Beta. Normally you'd progress from Alpha to Beta to RC to final, which are all manual updates. Though one should be only on released versions on a production server...that might be part of the problem here. Automatic updates will only install release versions.

You can try it and see. Worst case you need to install new and restore from a backup, which is where you are now.

ok, I'll try the update then.

As for having an alpha release, it was circumstantial, we are a government agency and we only completed the bidding process for a new license few days before the end of the current one, so we ended up in a rush.

And then, the same problem I'm having now happened, I was forced to upgrade in order to activate the new license. I could have done it to the latest v18, but I ended up in v20, alpha, which was kind a risky decision, I recognize. (But we only use the core functionality, no whistles and bells, so the probability to find a bug wouldn't be that much).

The intended procedure from now on will be as you described, only stable releases.

Thanks all for the help.

I'll try to update this thread after everything is settled down, for the record.

 

[gustavo.loureiro]

Hi.
So I updated the system to the latest stable release at the end of Friday, and everything went smoothly.
And so far, everything is going well, queues are queuing and transferring calls to available operators, individuals are placing and receiving calls, basically everything we use is doing its job.
Thanks all for the support.