Going around in circles with SIMS patch failing

[Sheridan]

We've been advised we need to run a patch by our LEA support (19098) to address a seperate issue - however I've tried about a dozen times and the deployment bombs out with this logged in the agent deployment log:

 

Failure - One or more errors occurred. - Package: fefc839d-0d84-45d6-bb32-2732e11a7cca - 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 05e6797e-b370-41cc-a4b7-da32d4668746 failed. ---> System.Data.SqlClient.SqlException:

 

No one was accessing SIMS at the time, I've made sure all the relevant services like Groupcall were stopped but I cannot get around this error!

 

Does anyone know what the above error actually means, as it doesn't seem to specify much about why it fails

[bknaggs]

How long does it take to get to the error state? If it's taking an hour or more it could be that your database is huge which can cause timeouts.

 

We had a problem when out database was over 60GB. The ulitmate solution was to manually run a patch to clear everything apart from the last 12 months worth of InTouch messages.

[Sheridan]

It only takes about 5 minutes to get that error - our database is about 38gb so large, but not massively so

[dapaulio]

5mins sounds like backup failure. Patches will perform a sql database backup. Check that you have sufficient space on sql backup location.

I can’t remember the exact threshold but I suggest having 2x database size of available space on the drive where the sql backup are located.

[Sheridan]

5mins sounds like backup failure. Patches will perform a sql database backup. Check that you have sufficient space on sql backup location.

I can’t remember the exact threshold but I suggest having 2x database size of available space on the drive where the sql backup are located.

 

Good call, but the backup seems to complete ok (and the DB is 38gb and we have 400gb free on the drive)

 

Edit: I had to run a different patch last night - and that worked fine, so it seems specific to this one

Edited May 2, 2024 by Sheridan

[dapaulio]

Good call, but the backup seems to complete ok (and the DB is 38gb and we have 400gb free on the drive)

 

Edit: I had to run a different patch last night - and that worked fine, so it seems specific to this one

 

Have you checked The patch is actually relevant to the database version you are on?

 

For example workstation patches are normally relevant to a certain major release.

[Sheridan]

Its applicable and we've been advised to apply it by the LEA and it doesn't show the error that its not valid (its a generic patch that you can run multiple times)

[dapaulio]

Is this the reindex patch by any chance?

If so keep running it. If you havent ran it for ages (or never ran it) it can fail multiple times before it completes successfully.

 

What you can do to help it complete

1- In solus extend the update timeout to minimum 60 mins.

2- Free up as much space as you can by removing old backups. (This is because a backup will be done every time you retry and will fill the hdd fast.

3- Restart the deployment service.

4- Then continually rerun the patch until it completes. It will likely complete

 

I run all housekeeping patches after every major update which keeps on top of it.

[Sheridan]

Thanks for the advice folks, in the end I had to run the relevant SQL scripts via SSMS directly - which worked ok! None the wiser why solus couldn't cope with it though!