Hi Aaron:

Sorry the upgrade didn't go smoothly. I suspect this is related to the increased checking for unknown modules that we added in 23.3. That unique constraint on module names ("uq_modulename") was added to catch potential issues, so sounds like either you have two modules with the same name or the server thinks you do. On a running server, you can see such unknown modules at the bottom of the module-details page, though if your server isn't starting up, you won't be able to see that page of course.

You should see the rest of the stack trace when you get that error, and it should include the name of the module violating the constraint. The full stack should be in the logs if not directly in the UI where you see the message. Does that help you identify what may have changed? If you see the name of a module that exists but has different casing (for example), try changing the casing to match. If it's a module that you used previously and dropped, try restoring it if possible (with the same name and casing) and see if that resolves this issue. Be aware with this latter option, of course, that module schemas can only be upgraded to 23.3 if they were previously on 22.1 (or later). Details are in our upgrade support policy.

If you need further assistance, please attach the full stack trace or log file, and tell us what version you were upgrading from, so that we can get a better idea of what might be going on.

Thank you for reaching out,

--Molly