Christina, I have had quite a few of these types of errors while attempting to upgrade from 20.05 to 21.05. What I have been forced to do is to manually add the missing fields to the tables directly. This is far from ideal, but rerunning the koha-update-schema does not seem to perform the missing changes. You need to see from the error message which field is missing and which table it is missing from. It is not too hard if you have direct access to the database and know how to edit the table structure. (I use a free software called HeidiSQL on windows which allows you to tunnel via SSH. Much easier than editing using the mysql command line.) If you have no experience editing the table structure directly, I don't have a good answer for you. Hope that helps Keith From: "Fairlamb, Christina" <cjf@wmu.se> To: koha@lists.katipo.co.nz Cc: Bcc: Date: Wed, 27 Jul 2022 09:34:17 +0200 Subject: [Koha] 500 errors in staff mode and forcing a database update Hello all, We've had these issues since at least Koha 21.11 but are now on 22.05. Some links on the koha staff page result in a 500 error. Checking the plack-error.log, these are the lines linking to the page I was trying to access: *EDI accounts* DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'me.responses_enabled' in 'field list' at /usr/share/koha/intranet/cgi-bin/admin/edi_accounts.pl line 110 *Library EANs* DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'me.ee_id' in 'field list' at /usr/share/koha/intranet/cgi-bin/admin/edi_ean_accounts.pl line 93 We also still have the Patron relationship problems issue in this bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24263, which should have been fixed during past upgrades. (values have been used for guarantee/guarantor relationships, but do not exist in the 'borrowerRelationship') It seems as though our database schema is not updating fully during our latest koha upgrades. I've tried to run the Manual schema upgrade which results in this message only: DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ bug_30899.pl [07:15:11]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) Which, according to this bug report: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899 - is a none issue and means the schema is up to date. Is there a way to force a schema update to go through all updates since a specific koha version? Christina