Every time I use SolidCP installer to update SolidCP Enterprise server, I have problems unless I do the following process :
(1) Stop the SolidCP Scheduler (to avoid locked-files errors)
(2) Use the SolidCP Installer to do the update
(3) Fix the database connectionString in binSolidCP.SchedulerService.exe.config (because the updater always breaks it; I just match the connectionString in web.config)
(4) Start the SolidCP Scheduler
This hasn't changed over many versions. It was very frustrating until I figured out the necessary steps. I suggest, please fix the installer so that it will do all of these steps automatically. Thanks.
By the way, I updated my installer to test this thoroughly with v1.4.4. For some unknown reason, the SolidCP.Installer.exe file in SolidCP-Installer-Update.zip just wouldn't run on this particular server, so I updated with SolidCPInstaller.msi -- which overwrote my SolidCP.Installer.exe.config so I needed to restore a backup of that file. It would be helpful if SolidCPInstaller.msi detected the existing config settings.
Thanks for posting this as I'm about to try and upgrade from 1.4.3 to 1.4.4 in the next couple of days
Hello,
This has indeed been an known issue since the first release.
The problem here is a limitation with the installer it self where we have so far not found any solution to find away around it.
It is why we always recommend to use the powershell update script instead, it does not come with this limitation and automated the process in full (including starting / stopping scheduler, and not deleting/overwriting it's config file).
Regards,
Marco
Seriously? Where do you recommend that, besides here?
I've avoided the powershell script because https://solidcp.com/kb/update/ indicates it's a Beta. Meanwhile https://solidcp.com/downloads/ gives no indication of which update method works best.
Is there another page that gives the best advice regarding how to update? Thanks.
In forum posts (not just this one), blog post about update release, homepage update release notification.
In the manual it indeed states beta (at time it was written was mid 2016) which is no longer the case. (hasn't been in quite a long wile).
