Jump to content

Recommended Posts

Posted

Is anyone else having a problem with the summer release? We have Solus 3 and scheduled the deployment however it failed to update the database (clients are updating fine) so we have an incompatible database error on clients. I have tried to update the database again and it still fails and proceeds to Rollback.

 

I have just got off the phone to Scomis who were at best useless which is unusual as they are normally very helpful. Anyone have any suggestions?

Posted (edited)

The only issue I can think of is the one in Solus - there is a Patch 23172 that states - 'Resolve issue in Upgrading to Summer 2017' - something to down with SQL and Latin1

 

Check your solus for patches

Edited by siuko
Posted
Mine jammed on a previous patch and failed to update entirely - I restarted the SOLUS service which cancelled it properly (always seem to lock up entirely otherwise), the deployment then worked fine.
Posted
There is an issue that is apparently very rare, the upgrade fails and should roll back to the Spring upgrade, although the one school we have had with it went into restricted user mode in SQL. There is a patch to run before the upgrade and one to run after to avoid the issue.
  • Thanks 1
Posted

05/07/2017 - (England, Wales and Northern Ireland) On demand Patch 23172 and 23173 released

 

We have received some calls from customers who have experienced some issues when upgrading their SIMS database to the Summer release. The error message presented is:

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.

 

To overcome this problem, customers are advised to apply patch 23172 to change the properties of the tables affected, then apply the Summer upgrade. Once the upgrade to Summer has been successfully applied, customers are then advised to apply patch 23173 to set the properties back to ensure the related applications work. Steps have been taken to ensure this does not happen in the Autumn upgrade.

Posted
I had to upgrade to the database only release .768 and then to the full release which has a second .771 version number.
Posted

We are doing this next week. I won't lie but every time I click deploy I have my mind fingers crossed that all goes well.

 

Rarely ever perform them outside of holiday periods so we can contact Capita asap and it's not the end of the world if it's not fixed in 2 minutes.

Posted

I have resorted to restoring the database from before the attempted upgrade, just for information patch 23172 failed too. I have sent log files to Capita hopefully they will have an answer.

 

No more attempts till the holiday.

Posted
Tried last week and the Database upgrade failed. Rolled back to Spring - but the Summer update is needed for exams. Had to supply a copy of our database to Capita - they are still working on the problem a week later.... They say that doind a database only upgrade first is not advised and the patch mentioned is not applicable to us - so I've got no option but to wait for a fix.
Posted

Tried 6 times today to put the Summer release on every time failed with 'Tolerance not met for target SIMS Database'

 

The Discover update went on ok so SOLUS itself is working.

 

Found this thread, and applied that patch 23172 then the Summer upgrade went on a charm.

 

Thanks!

Posted
Tried last week and the Database upgrade failed. Rolled back to Spring - but the Summer update is needed for exams. Had to supply a copy of our database to Capita - they are still working on the problem a week later.... They say that doind a database only upgrade first is not advised and the patch mentioned is not applicable to us - so I've got no option but to wait for a fix.

 

Doing the database only upgrade (before doing the full upgrade) worked fine for us. No issues at all.

Posted
How the hell does that sneak through testing?

 

Currently the are eight reported incidents of this problem (PRB16298). It is caused by the existence of two category types with the same description (“Level”) something that SIMS does not permit hence it was not in a test scenario. It is not currently known how this has arisen though we can speculate that it may be due to migration from another system, or more lax validation rules in earlier versions of SIMS.

 

Escalations are investigating the impact of a pre-upgrade patch to rename the duplicate category and allow the upgrade to be applied.

  • Thanks 2
Posted
I was chatting with a guy at our local support unit, it is to do with a couple of specific tables which use a slightly different Latin character set for validation, there are two patches to run, one before the update which converts those tables to the same as the rest of the SIMS database and then one that converts it back afterwards. Word is that they are working on unifying this character set issue for autumn to unify the database.
  • Thanks 1
Posted
Just from chatting to there techs round my area there are way more than that.

 

I can only go on reported cases. ~650 schools have upgraded so far.

Posted

the last couple of upgrades have listed the database update separately to the main release i thought makes it easier to see what actual DB version you are when it comes to seeing what other patches will apply.

 

The number of patches for SIMS after upgrades does seem to be on the increase.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...