We just backed up and migrated from v15 to v17 I moved my activation over to v17 for commercial module and after the fact I realized that none of our EPM templates rolled over.
Now because i moved my activation I am unable to pull those via GUI either.
Is it possible to export the configs from the v15 machine and import them into the v17 machine?
Good grief, yet another Borked upgrade. @Sangoma, can you please either fix this process, even if itâs just reporting failures, or document all the broken bits for us poor admins trying to use it??
Could you please try the restore process again if you have a backup of the just endpoint module.
Alternatively, if you havenât made any modifications or created new configurations in v17 yet, you can attempt the restore the full backup once more.
Please note that commercial modules depend on an active license for a smooth restore process. I suspect that if the restore was performed before activating the system, it may have caused this issue. I suggest reattempting the restore process on a âlicensedâ v17 system to resolve the problem.
Wishing you and your family a very Happy New Year 2025(in advanced)!
Best regards,
Kapil
Are you sure about this? Iâve restored v14, v15 and v16 systems to new systems or even Advanced Recovery systems before the licensing was completed on said systems. Never once have I had this issue of non-licensed modules messing up the restore.
@kgupta So it is Sangomaâs official position that in order to restore FreePBX from previous versions to FreePBX v17 it is going to require the person to license a second set of modules just to make sure the restoration of the backup is done with no errors? Because this logic is highly flawed as it requires the user to do one of two things.
I guess there is a third option which is the same as option 2 but they move production to v17 and just deal with any bugs or issues hoping theyâll get resolved as fast as possible by support which hasnât had a great track record so far with this. Either way, all the options suck if this is the logic being followed by Sangoma.
@FreerPBXer Have all of your restored systems with issues involved licensed commercial modules? I canât replicate issues with restores from older version but these are also from systems that do not have any commercial modules licensed on them. I can test one with commercial modules this week.
That might be technically correct (emphasis on âmightâ), but the upgrades we do also have the step of transferring the activation before the restore, and FreePBX (removed profanity and substituted âFreePBXâ) still breaks. Every. Time.
There is simply no way I can see that you are doing any sort of proper testing of the upgrade paths that imitates a production system and consistently results in completely successful upgrades.
Sorry about the lack of response everyone!
It looks like when I made my initial backup I did not have the the EPM module checked off. Then when I deactivated old server, restored the backup and realized EPM wasnât part of it. I went back into old system and EPM was not even an option in the list of modules.
I ended up moving activation back to old server and all the sudden EPM was available in the list of modules, so I created a back up with just EPM in it and restored it to the new machine and all is good.
I am getting a Database error for unknown column now. (SQLSTATE[42S22]: Column not found: 1054 Unknown column âplarNumberâ in âfield listâ)
I think I just need to reinstall endpoint but not totally sure how to do that.
We have pushed endpoint v17.0.2.3 today with the fix, can you please try this version @bpatterson117
fwconsole ma downloadinstall endpoint --tag=17.0.2.3