For info if any of you are planning on moving SOLUS3 to a new server any time soon, or if you already have done and have SOLUS3 self upgrade failures...
The KB ref for Capita's notes is: KB115891
We have had 30+ schools where SOLUS3 has failed to self upgrade from 3.4.118 to 3.5.20. All sites failed at the database stage with the same error and rolled back to 118. I logged a call with Capita and it seems that this is an issue that affects schools where SOLUS3 has been moved from an old server to a new server in the past (all our sites that failed have had SOLSU3 moved to a new server). Capita's SOLUS3 migration guidance originally instructed you to detach the SOLUS3 database on the old server and then attach to the new server.
This has now been identified as incorrect and will cause future SOLUS3 database self updates to fail and roll back. You have to in fact detach the database on the old server, and then use the manual installer to install a new, blank database on the new server as the manual installer also installs a number of stored procedures (or something similar). You then have to delete the blank database via management studio and attach the old database. Simply detaching and reattaching does not transfer the stored procedures that are used by SOLUS3 to self upgrade.
We've been told to upgrade each of these databases manually using the manual installer, then we should be able to run the rest of the SOLUS3 upgrade using SOLUS3 itself. Capita's new notes reflect this new guidance so be sure to update your instructions.
Thanks for the heads up, I was looking to migrate over the next month or so so I better make sure I have the most up-to-date documentation.
There are currently 1 users browsing this thread. (0 members and 1 guests)