Ive tried numerous approaches to get the upgrade power-shell to complete a test on our upgrade before running the upgrade to the latest version of solid to no success.
When running the powershell applet with option three, and error is returned and then cleared within a second, which does not provide enough time to review the log and see where it is failing.
We have solidcp enterprise and portal server installed on the same server with a remote MS SQL database server.
We're currently running v 1.2.1 - trying to upgrade to version 1.3
After much frustration I tried the manual update process and ran into further issues, and then had to recover from backup in order to get solidcp functional again.
Any help / suggestions would be appreciated.
A quick update, for some reason I am now able to review the error log
Invoke-SQLCmd : Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
At C:UsersAdministratorDownloadsSolidCP-Auto-Upgrade-Tool-1.6SolidCP-Auto-Upgrade-Tool-1.6SolidCP-Auto-Upgrade.ps
1:173 char:36
+ push-location ; ($SCP_UNC_Test = Invoke-SQLCmd -query "SELECT [ServerName], [S ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Invoke-Sqlcmd], SqlException
+ FullyQualifiedErrorId : SqlExectionError,Microsoft.SqlServer.Management.PowerShell.GetScriptCommand
Invoke-SQLCmd :
At C:UsersAdministratorDownloadsSolidCP-Auto-Upgrade-Tool-1.6SolidCP-Auto-Upgrade-Tool-1.6SolidCP-Auto-Upgrade.ps
1:173 char:36
+ push-location ; ($SCP_UNC_Test = Invoke-SQLCmd -query "SELECT [ServerName], [S ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ParserError: (:) [Invoke-Sqlcmd], ParserException
+ FullyQualifiedErrorId : ExecutionFailureException,Microsoft.SqlServer.Management.PowerShell.GetScriptCommand
Hello,
The auto upgrade tool should normally work fine aslong as it's executed from the Enterprise server and ran in an administrator priveledged powershell.
The most easy way is to simply open a administrator level powershell (right click run as administrator) --> cd c:yourlocation --> then ./nameofpowershell.ps1
this should for sure keep any error visible without closing.
In your errors case i see: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
Which indicates the user your executing the script with has no SQL access (the windows user will need sysadmin access).
Regards,
Marco
Thanks for the response Marco,
With regards to sql login failure... our solidcp is hosted on another server.
Can the upgrade script not read the connection string values from the .config files rather than assuming that it requires windows credentials?
Any possible work around to the above for now?
An update, just tested running the upgrade script with elevated privileges and still get the same outcome - an error is returned but then disappears within a few 100 milliseconds
