Hi @dormosh ,
Is the Portal running on the same server as your Enterprise Server?
I will look at writing a catch in to cater for this, but for the time being if you could run the script on your Enterprise Server and select to just upgrade the Enterprise Server.
I would also recommend downloading the latest version of the script as we have updated some bits.
Please let us know how you get on.
Kind regards,
Marc
Hello,
Yes, the portal is running in the same server where enterprise server is. Moreover, I used the latest script.
It worth mentioning also that the script assumes that the sql server is in the same server where enterprise server is. I think the sqlcmd command can be modified to include the user/password of the sql server.
To let people know:
This script only works on Windows Server 2012 and up because it use some functions only avalaible in 2012 like "New-SMBShare".
New-SMBShare : The term 'New-SMBShare' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:SolidCP-Auto-Upgrade.ps1:401 char:6
+ New-SMBShare -Name "SCPUpgrade$" -Path "$SCP_UpdateDirEnterprise Server - ...
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (New-SMBShare:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundExceptionBackup-SqlDatabase : System.Data.SqlClient.SqlError: Cannot open backup device
'192.168.46.1SCPUpgrade$WebsitePanel - 2018-02-20 - (14.52 PM).bak'. Operating system error 67(The network name
cannot be found.).
At C:SolidCP-Auto-Upgrade.ps1:407 char:7
+ Backup-SqlDatabase -ServerInstance "$SCP_Database_Servr" -Database "$SCP_D ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Backup-SqlDatabase], SmoException
+ FullyQualifiedErrorId : ExecutionFailed,Microsoft.SqlServer.Management.PowerShell.BackupSqlDatabaseCommand
Regards
--
Hello,
the SMB share error is not a problem, it just means you need to manually backup SQL before starting, then simply use the 1.6 script which continues after backup error --> the rest works fine.
Regards,
Marco