Could (or could not) be a issue somehow related with the problem I’ve had shortly, when trying to import a zammad 3.2 db dump on a fresh new zammad 3.4 installation - here are all the details: Upgrading Zammad from version 3.2 to version 3.4
TLDR: after importing the db dump on the zammad 3.4 installation try running “rails zammad:db:init” - might be worth a try…