We have released a script to upgrade your SolidCP deployment to the latest version, but the tool can be used to test the latest BETA version as well.
There is an article about this here https://solidcp.com/kb/update/solidcp-update-script-powershell/
We would welcome any feedback regarding the script as it is still in BETA stage.
The script will upgrade all of your current SolidCP environment to the latest stable version of SolidCP or the latest BETA version of SolidCP and will take a FULL backup of each component that is upgraded.
DO NOT use this script to upgrade from Website Panel or MSP Control as it has been written to upgrade existing SolidCP deployments ONLY.
Hello All. We upgraded our WSP to Solid CP using https://solidcp.com/kb/installation/migrate-websitepanel-solidcp/ which resulted in version 1.0.3 running.
When I attempt to use the Auto Upgrade Powershell script, I get:
The term ‘Invoke-SQLCmd’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check t
he spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:SolidCP-Auto-Upgrade-ToolSolidCP-Auto-Upgrade.ps1:164 char:49
+ push-location ; ($SCP_UNC_Test = Invoke-SQLCmd <<<< -query “SELECT [ServerName], [ServerUrl] FROM [$SCP_Data
base_Name].[dbo].[Servers] WHERE [VirtualServer]=’0′” -Server $SCP_Database_Servr) | Out-Null ; Pop-Location
+ CategoryInfo : ObjectNotFound: (Invoke-SQLCmd:String) , CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
I assume it is because my enterprise server is not on the same server as my SQL server?
Any fix for this? Is there an easy way to move Enterprise server to my SQL server if that is the fix? Before I go and break everything, I thought I better ask.
- Views27481 times
- Answers34 answers