Solved Assistance Required: Reverting to v18.9.0.35 for PBX Restoration

Status
Not open for further replies.

diegocardenas1970

Customer
Joined
Jan 26, 2025
Messages
4
Reaction score
2
Hi All,

While upgrading our system from version 18.9.0.35 to v20, I inadvertently neglected to properly set up the system owner. As a result, when I attempted to run v20, I was unable to see phones or extensions under the account I believed was set up as the system owner.

To address this, I need to revert back to v18.9.0.35, restore my backup, correctly configure the system owner, and then create a new backup before proceeding with the upgrade again.

The challenge I am facing is that the latest build I’ve been able to locate is v18.9.0.31. When attempting to restore, the system notifies me of the version mismatch, and I am unable to proceed.

Would anyone have a link or resource where I can download the v18.9.0.35 build of the PBX?

Thanks in advance for your assistance!

Best regards,
DC
ERX
 
In addition when I try to revert to an older backup that can be used by older executables I am now getting this....

"Product cannot be activated because the license key is of a previous version. Upgrade license key or purchase maintenance from https://customer.3cx.com/orderform/default.aspx"

From what I have read once your license has been upgraded to v20 it can not be donwgraded to make fixes or changes to then re update to v20!

Is there ANY way to add a system owner role to a user on a v20 roll out?

It seems like I am stuck on a v20 with no owner and the ability not to be able to downgrade to make changes? Anyone with any ideas on how to resolve?
 
Stay on v20.

Scrap the VM and spin up a new one.

If your backup isn't encrypted, open in 7zip/WinRAR, edit the XML file inside and search for your email/extension number. Looks for the Roles attribute and change (probably) "owners" to "system_owners" (or whatever it was). Save, update ZIP and then use that to restore. Use that occasion to check for unique emails, make sure your system owner has a unique email.
 
Stay on v20.

Scrap the VM and spin up a new one.

If your backup isn't encrypted, open in 7zip/WinRAR, edit the XML file inside and search for your email/extension number. Looks for the Roles attribute and change (probably) "owners" to "system_owners" (or whatever it was). Save, update ZIP and then use that to restore. Use that occasion to check for unique emails, make sure your system owner has a unique email.
Thank you Ill give that a try to see if I get the right label for that user role and I am able to get that extension as the system owner
 
Stay on v20.

Scrap the VM and spin up a new one.

If your backup isn't encrypted, open in 7zip/WinRAR, edit the XML file inside and search for your email/extension number. Looks for the Roles attribute and change (probably) "owners" to "system_owners" (or whatever it was). Save, update ZIP and then use that to restore. Use that occasion to check for unique emails, make sure your system owner has a unique email.
Hi CW

It seems like that has done it!

They key for me was to use 7zip and work on the file without decompressing the archive.
On my 1st attempt I tried to work on the XML by creating a backup of the backup, decompressing it using the zip client built into windows byt when I re-zipped the file 3cx when restoring said the file was corrupted.

After that I worked on the file using 7zip. Located the role for that extension and made it the "system_owners", I als made sure no other extension was set to the same role.

Thanks
DC
 
Status
Not open for further replies.

Forum statistics

Threads
112,293
Messages
591,747
Members
165,420
Latest member
x1515