Solus 3 - 3.10.73 Deployment - Tolerance not met for target Solus 3 Database.

[Ghostdancing]

Hi

 

Trying to install the Solus 3 - 3.10.73 Deployment but I am getting the following issue.

 

Tolerance not met for target Solus 3 Database, deployment stopping.

 

I have attached the log file, if anyone can help me with this issue.

 

Thanks

ddp_ds_9fc75b57-3eb3-4ae0-b0c9-7bb08452c848.txt

[CyberDrac]

I had that ... passed it to our off site SIMS support team (EIS Kent) who had to bring in the Capita big guns.

Never got an explanation of what they did but it took an afternoon of them prodding around on the SQL server.

[bossman]

@MarkPurvis

 

It maybe that the version you have at the moment is not what the new version is expecting, you may have to upgrade to a version closer before you can go to the latest version, had this once with a Sims database version when I tried to update, I had missed out an incremental version in between.

 

It could also be that the download is corrupt, try downloading the update again

Edited January 14, 2016 by bossman

[kshah58]

Hi

 

Trying to install the Solus 3 - 3.10.73 Deployment but I am getting the following issue.

 

Tolerance not met for target Solus 3 Database, deployment stopping.

 

I have attached the log file, if anyone can help me with this issue.

 

Thanks

 

Had a look at the log file...SOLUS 3 is currently on version 3.9.0.17?

 

Try and change the Authentication type to SQL in the SOLUS 3 settings in your SOLUS 3 Deployment Server UI, save it, restart the deployment service, and redeploy the SOLUS 3.10 upgrade. If this still gives you an error, open SQL Management Studio and give NT AUTHORITY\SYSTEM db_owner permission under User Mapping for the SOLUS 3 database. Restart the deployment service and redeploy the SOLUS 3.10 upgrade. Hopefully this should work.

 

If this still does not work...then have you downloaded the 3.10 installer files from Capita?

 

If you have, then uninstall the SOLUS 3 database from Programs and Features via Control Panel. Run SOLUS3DeploymentServerDatabase.exe adding the server instance, select the SQL Authentication option, add the SQL user (usually "sa") and the password, click test connection in which you will get the message stating that the database already exists and will upgrade to the latest version. Click Next and the database will then upgrade. Check if the SOLUS 3 database is present in the list of Programs and Features and check the version as well.

 

Go back into SOLUS 3 Deployment Server UI and redeploy the 3.10 upgrade. Since the database has been upgraded the deployment should skip to the Deployment Service, GUI and Agent.

 

It looks like a long workaround but in truth it only takes around 10 minutes to do.

 

Good luck and see how you get on!

 

Regards,

 

Kunal

[DarkMaster]

Had a look at the log file...SOLUS 3 is currently on version 3.9.0.17?

 

Try and change the Authentication type to SQL in the SOLUS 3 settings in your SOLUS 3 Deployment Server UI, save it, restart the deployment service, and redeploy the SOLUS 3.10 upgrade. If this still gives you an error, open SQL Management Studio and give NT AUTHORITY\SYSTEM db_owner permission under User Mapping for the SOLUS 3 database. Restart the deployment service and redeploy the SOLUS 3.10 upgrade. Hopefully this should work.

 

 

Thanks this worked for me with Solus 3.10.88.4

[JHLEHS]

There's a patch which does the same thing the patch number is 18985

[IWDave]

"So examined the SOLUS 3 updates page and found a Database that was potentially newer than the one we had."

 

From what I've experienced in the past, Capita release database updates ahead of the main update, I then schedule these updates in before the main update. Bizarrely even though these database updates are present, the main update doesn't see them, and fails.

 

Would you like to know more? https://www.daveiw.co.uk/wp/?p=156581 AND https://www.daveiw.co.uk/wp/?p=345162

Edited April 27, 2016 by IWDave
Two web links

[Willott]

The other thing to watch out for is the fun of having moved a Solus 3 DB between instances - looks like the instance is stored in SQL and the package deployer looks this up - ours was trying to do stuff on our old instance as part of the install. Table solus3.agent_target_parameters, check against solus3.agent_target to find the relevant instancename and ensure this matches solus3 instance

[bossman]

Also sometimes when cleaning out the old downloads from the install directory you can inadvertently remove base infrastructure update files that Solus3 requires which also happened to me when migrating to another server, all I did was download all the base infrastructure updates within Solus3 and that seemed to cure the problem.

[ALittleFish]

I believe the issue is caused by Solus3 not picking up the target information correctly for the Solus3 targets (Database, Services, UI) which in older versions we can't actually see. From 3.10 onwards we are able to view the Solus3 targets in Settings | Solus3 | Show SOLUS3 targets (Blue Hyperlink)

 

I have two ways around this issue both of which I've used plenty of times on our schools in the past but mainly number 2.

 

1: Within Solus3 Settings | Solus3. Reset the Service Host back to the Solus3/SIMS Server.

--To do this you need to select a different computer or server (Select one from random in the Agents list.), [ignore the warning message about Solus3 not working if the wrong computer is selected. As we're not going to save these settings.]

---Then change the Service Host back to the correct Solus3/SIMS Server and Save the settings.

- Redeploy the Solus3 upgrade and see if this has worked.

 

2: Manually upgrade the Solus3 database and then redeploy the upgrade through Solus3.

--Extract the Solus3 upgrade from Solus

---Then manually upgrade the Solus3 database by running the Solus3DeploymentServerDatabaseInstaller.msi. (This will pick up that the a Solus3 database is already installed and just upgrade it.)

-Redeploy the Solus3 upgrade in Solus3.

As the Solus3 database is now already upgraded it won't fail during the deployment. It may go over the Solus3 database again but can't fail as the upgrade is already applied.

Edited April 29, 2016 by ALittleFish