tech-man Posted May 11, 2015 Posted May 11, 2015 Hello I am trying to upgrade my SOLUS from 3.6 to 3.9, the system tells me I need to install 3.7 first. When trying to install 3.7 it fails... does anyone have any ideas why? It fails around 19:59 Thanks SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|AgentEnvironmentVariables - ___SIMSDiscoverDirectory: SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|AgentEnvironmentVariables - ___NovaSatellite: SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|AgentEnvironmentVariables - ___SIMSConnection_ServerName: SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|AgentEnvironmentVariables - ___SIMSConnection_DatabaseName: SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|AgentEnvironmentVariables - ___FMSConnection_ServerName: SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|AgentEnvironmentVariables - ___FMSConnection_DatabaseName: SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|Package deployer deploying 'Solus 3 - 3.7.161.0 (Solus 3 Database solus3_deployment_server)' SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|Unpacking packages SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|Packages unpacked SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|Deploying package 1 of 1 SIMSSRV|11/05/2015 19:59:14|PackageDeploymentManager|Starting package runner for package 'Solus 3 - 3.7.161.0'. Mode: Backup SIMSSRV|11/05/2015 19:59:14|PackageRunner|Running package, 'Solus 3 - 3.7.161.0' SIMSSRV|11/05/2015 19:59:14|PackageRunner|Verifying package signature SIMSSRV|11/05/2015 19:59:15|PackageRunner|Verified package signature SIMSSRV|11/05/2015 19:59:15|PackageRunner|Verifying files signature SIMSSRV|11/05/2015 19:59:15|PackageRunner|Verified files signature SIMSSRV|11/05/2015 19:59:15|PackageRunner|Validating package SIMSSRV|11/05/2015 19:59:15|PackageRunner|Validated package SIMSSRV|11/05/2015 19:59:15|PackageRunner|Starting task set runner in backup mode for package, 'Solus 3 - 3.7.161.0' SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Running task set in Backup mode - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Number of tasks: 1 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Persisting task ID, 5b88d4a1-a329-412e-9328-5a6b19811030 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Running task, 'Upgrade database', in Backup mode. - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TaskRunner|Attempting back up for task, 'Upgrade database' - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TaskRunner|Backup completed - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Result was Ignored for task 'Upgrade database' with message 'Task does not implement rollback strategy.' - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|PackageRunner|Task set runner completed in backup mode SIMSSRV|11/05/2015 19:59:15|PackageRunner|Starting task set runner in install mode for package, 'Solus 3 - 3.7.161.0' SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Running task set in Install mode - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Number of tasks: 1 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Persisting task ID, 5b88d4a1-a329-412e-9328-5a6b19811030 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TasksetRunner|Running task, 'Upgrade database', in Install mode. - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|TaskRunner|Running task, 'Upgrade database' - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: Installer GUID: 56a1a385-e82f-4ed2-a9b1-0341df6cecbe - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: filename:C:\ProgramData\Capita\Solus3\Deployments\dbf3cfb4-7dac-4ddc-b0df-c45a87fdec65\Packages\844becd6-4d74-4eb2-94e9-37018e131040\Unpack\SOLUS3DeploymentServerDatabaseInstaller.msi - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: Changed to install mode [Only relevant for Terminal Servers] - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: started process - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|ExecuteInstaller|ExecuteInstaller: exit code was 1603 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|ExecuteInstaller|ExecuteInstaller: Changed back to execute mode [Only relevant for Terminal Servers] - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|PackageRunner: Install failed. Exception: Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 5b88d4a1-a329-412e-9328-5a6b19811030 failed. ---> System.ApplicationException: ExecuteInstaller: Unsuccessful installation because exit code was 1603 at Sims.Solus3.Deployment.Tasks.ExecuteInstaller.ExecuteTheInstaller(String fileName, String options) at Sims.Solus3.Deployment.Tasks.ExecuteInstaller.InternalExecute(TaskExecutionInfo taskData) at Sims.Solus3.Agent.PackageDeployer.TaskRunner.Run(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progressUpdater) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTask(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) --- End of inner exception stack trace --- at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTask(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTaskSet(DecompiledTaskset taskset, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.Run(DecompiledTaskset taskSet, DecompiledPackage package, IProgressUpdateSubscriber progressUpdater) at Sims.Solus3.Agent.PackageDeployer.PackageRunner.Run(DecompiledPackage package, IProgressUpdateSubscriber progress, Boolean backup) - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|PackageRunner|Starting task set runner in rollback mode for package, 'Solus 3 - 3.7.161.0' SIMSSRV|11/05/2015 19:59:26|TasksetRunner|Running task set in Rollback mode - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TasksetRunner|Number of tasks: 1 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TasksetRunner|Continuing from task id 5b88d4a1-a329-412e-9328-5a6b19811030 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TasksetRunner|Persisting task ID, 5b88d4a1-a329-412e-9328-5a6b19811030 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TasksetRunner|Running task, 'Upgrade database', in Rollback mode. - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TaskRunner|Attempting rollback for task, 'Upgrade database' - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TaskRunner|Rollback completed - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|TasksetRunner|Result was Ignored for task 'Upgrade database' with message 'Task does not implement rollback strategy.' - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|PackageRunner|Task set runner completed in rollback mode SIMSSRV|11/05/2015 19:59:26|Failure - One or more errors occurred. - Package: 844becd6-4d74-4eb2-94e9-37018e131040 - More Info: System.AggregateException: One or more errors occurred. ---> Sims.Solus3.Agent.PackageDeployer.PackageException: Package failed. Rollback was executed. ---> Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 5b88d4a1-a329-412e-9328-5a6b19811030 failed. ---> System.ApplicationException: ExecuteInstaller: Unsuccessful installation because exit code was 1603 at Sims.Solus3.Deployment.Tasks.ExecuteInstaller.ExecuteTheInstaller(String fileName, String options) at Sims.Solus3.Deployment.Tasks.ExecuteInstaller.InternalExecute(TaskExecutionInfo taskData) at Sims.Solus3.Agent.PackageDeployer.TaskRunner.Run(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progressUpdater) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTask(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) --- End of inner exception stack trace --- at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTask(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTaskSet(DecompiledTaskset taskset, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.Run(DecompiledTaskset taskSet, DecompiledPackage package, IProgressUpdateSubscriber progressUpdater) at Sims.Solus3.Agent.PackageDeployer.PackageRunner.Run(DecompiledPackage package, IProgressUpdateSubscriber progress, Boolean backup) --- End of inner exception stack trace --- at Sims.Solus3.Agent.PackageDeployer.PackageRunner.Run(DecompiledPackage package, IProgressUpdateSubscriber progress, Boolean backup) at Sims.Solus3.Agent.PackageDeployer.PackageDeploymentManager.LaunchPackagRunner() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of inner exception stack trace --- ---> (Inner Exception #0) Sims.Solus3.Agent.PackageDeployer.PackageException: Package failed. Rollback was executed. ---> Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 5b88d4a1-a329-412e-9328-5a6b19811030 failed. ---> System.ApplicationException: ExecuteInstaller: Unsuccessful installation because exit code was 1603 at Sims.Solus3.Deployment.Tasks.ExecuteInstaller.ExecuteTheInstaller(String fileName, String options) at Sims.Solus3.Deployment.Tasks.ExecuteInstaller.InternalExecute(TaskExecutionInfo taskData) at Sims.Solus3.Agent.PackageDeployer.TaskRunner.Run(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progressUpdater) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTask(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) --- End of inner exception stack trace --- at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTask(DecompiledTask task, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.RunTaskSet(DecompiledTaskset taskset, DecompiledPackage package, IProgressUpdateSubscriber progress, TaskAction action) at Sims.Solus3.Agent.PackageDeployer.TasksetRunner.Run(DecompiledTaskset taskSet, DecompiledPackage package, IProgressUpdateSubscriber progressUpdater) at Sims.Solus3.Agent.PackageDeployer.PackageRunner.Run(DecompiledPackage package, IProgressUpdateSubscriber progress, Boolean backup) --- End of inner exception stack trace --- at Sims.Solus3.Agent.PackageDeployer.PackageRunner.Run(DecompiledPackage package, IProgressUpdateSubscriber progress, Boolean backup) at Sims.Solus3.Agent.PackageDeployer.PackageDeploymentManager.LaunchPackagRunner() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute()<--- SIMSSRV|11/05/2015 19:59:27|DeploymentOrchestrator|Deployment completed SIMSSRV|11/05/2015 19:59:27|DeploymentOrchestrator|Told GUI deployment is finished SIMSSRV|11/05/2015 19:59:27|DeploymentOrchestrator|Clearing current deployment. SIMSSRV|11/05/2015 20:01:40|DeploymentOrchestrator|Starting deployment of .NET Framework 4.5 (Solus 3 GUI ) in Rollback mode. SIMSSRV|11/05/2015 20:01:40|DeploymentOrchestrator|Starting download SIMSSRV|11/05/2015 20:01:40|DeploymentOrchestrator|Download complete SIMSSRV|11/05/2015 20:01:40|DeploymentOrchestrator|Deployment status set to DueDeployment SIMSSRV|11/05/2015 20:01:41|DeploymentOrchestrator|Told GUI deployment scheduled SIMSSRV|11/05/2015 20:01:41|DeploymentOrchestrator|Deployment status set to ExecutingPackages SIMSSRV|11/05/2015 20:01:41|DeploymentOrchestrator|Told GUI deployment started SIMSSRV|11/05/2015 20:01:41|DeploymentOrchestrator|Loading package deployer SIMSSRV|11/05/2015 20:01:41|DeploymentOrchestrator|Package deployer loaded
matt40k Posted May 11, 2015 Posted May 11, 2015 The MSI installer has balls up. Looks like you might have to rip it out and reinstall it (the MSI that is). Give support a call tho.
Cache Posted May 11, 2015 Posted May 11, 2015 (edited) SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: filename:C:\ProgramData\Capita\Solus3\Deployments\ dbf3cfb4-7dac-4ddc-b0df-c45a87fdec65\Packages\844becd6-4d74-4eb2-94e9-37018e131040\Unpack\SOLUS3DeploymentServerDatabase Installer.msi - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: Changed to install mode [Only relevant for Terminal Servers] - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:15|ExecuteInstaller|ExecuteInstaller: started process - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|ExecuteInstaller|ExecuteInstaller: exit code was 1603 - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|ExecuteInstaller|ExecuteInstaller: Changed back to execute mode [Only relevant for Terminal Servers] - Package: 844becd6-4d74-4eb2-94e9-37018e131040 SIMSSRV|11/05/2015 19:59:26|PackageRunner: Install failed. Exception: Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 5b88d4a1-a329-412e-9328-5a6b19811030 failed. ---> System.ApplicationException: ExecuteInstaller: Unsuccessful installation because exit code was 1603 That's the bit with the problem and looks similar to the issue I had after moving Our deployment across to Server2012/SQL 2012. Capita had to make various changes to our setup to correct it, it's something to do with the dbo user not being set to SA or System not having an account called System, I don't remember getting the full reasoning behind it, only an assurance that next time a Solus Update comes out I wouldn't have an issue. Check event viewer and see if you have an error in the application log starting something similar to the following against msiexec: Product: SOLUS 3 Deployment Server Database -- Error 26204. Error -2147217900: failed to execute SQL string, error detail: User or role 'NT AUTHORITY\SYSTEM' does not exist in this database., SQL key: ApplyReaderWriterPermissions_SQL SQL string: use solus3_deployment_server; If it is the same issue, a quick fix is to download the Solus 3 packages from SupportNet/My Account and manually run the installer and then push the upgrade out to upgrade the agents. Edited May 11, 2015 by Cache 1
matt40k Posted May 11, 2015 Posted May 11, 2015 Quick fix would be to give NT AUTHORITY\SYSTEM db_owner to solus3_deployment_server database, surely?? 1
Cache Posted May 11, 2015 Posted May 11, 2015 (edited) NT Authority\System already had an account when it tried to create one though (it just wasn't called NT AUTHORITY\SYSTEM which is what it was looking for) and I chickend out at that point for fear of breaking anything else. Edited May 11, 2015 by Cache 1
tech-man Posted May 11, 2015 Author Posted May 11, 2015 Seeing a couple of errors in event viewer: Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'solus3_deployment_server'. [CLIENT: ] & then Product: SOLUS 3 Deployment Server Database -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action LaunchSqlPackage, location: C:\Program Files (x86)\Solus3\Deployment Server Database\, command: ********** Any suggestions?
Cache Posted May 11, 2015 Posted May 11, 2015 Looks similar to our error. I would take a stab at looking in SQL Management Studio at your solus3_deployment_server database under Security -> Users and see if NT AUTHORITY\SYSTEM is listed there or not. If it isn't, I would guess adding an account with the login NT AUTHORITY\SYSTEM with the login name NT AUTHORITY\SYSTEM and the schema dbo, memberships db_datareader, db_datawriter, db_owner, db_securityadmin would probably do it. That is how our NT AUTHORITY\SYSTEM is configured on the server, however I'm always wary of tinkering with it - I'd be more tempted to log it with Capita in the morning for them to look at it. If you atleast see if it is listed as a login against the database you know whether it's going in the right direction or not. you could also try using the connection string editor for the deployment service to alter it to use SA instead of the local system account. If it was me, I'd leave it and log it in the morning but only because I don't like meddling with databases unless I know what I'm doing or I wrote it. 1
tech-man Posted May 11, 2015 Author Posted May 11, 2015 I've just done that anyway. Now rerunning....
tech-man Posted May 11, 2015 Author Posted May 11, 2015 Different error this time: Product: SOLUS 3 Deployment Server Database -- Error 26204. Error -2147217900: failed to execute SQL string, error detail: User does not have permission to perform this action., SQL key: CreateMachineLogin_Trusted SQL string: IF NOT EXISTS (SELECT name FROM master.sys.server_principals WHERE name = 'DOMAIN\SIMSSRV$') BEGIN CREATE LOGIN [DOMAIN\SIMSSRV$] FROM WINDOWS WITH DEFAULT_DATABASE=[master] END
tech-man Posted May 11, 2015 Author Posted May 11, 2015 OK - so it now looks like the upgrade has worked... how can I verify that the database upgrade aspect of it has happened? What tables or other bits are new in the DB? I have new GUI (yuck) & agents deployed.
Cache Posted May 11, 2015 Posted May 11, 2015 Not 100% sure. It is listed in the database somewhere but I didn't see/can't remember where. Simplest way which was normally reliable I think is to go to your Upgrade Library, click on Deploy for the version you've just deployed or 3.9 and then scroll down the targets until you come to Solus 3 Database and the current version will be listed there.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now