Specify 7 – Error when saving data in Collection Object + data not visible

Get Help
1

#Specify 7 Version:v7.11.0.2(debug)
Hi everyone,
I’m Mattia and I’m currently working with Specify 7 at the Stazione Zoologica Anton Dohrn in Naples, Italy.

We recently installed Specify 7, but I’m encountering a recurring issue: when I try to enter data in the Collection Object field and click save, I get this error message:

"We’re sorry, it seems you have encountered an error in Specify 7 that we may not be aware of. To avoid corrupting data records, you need to start again from a safe spot–the Home page.

If this issue persists, please contact your IT support. If this is a Specify Cloud database, please download the error message and send it to support@specifysoftware.org."

I’ve already tried clearing the cache and using different browsers, but the problem still occurs. Sometimes it tries to load, but the “Loading” message stays on the screen for over 30 minutes, and nothing gets saved.

The same error also occurs when I try to work with Workbench.

In addition, the data that is available and visible in Specify 6.8 does not appear in Specify 7.

Has anyone else experienced this issue or found a fix?
Thanks a lot in advance – I’m looking forward to any suggestions or feedback.

2

Hi @mattia.paparo,

Thank you for reaching out!

Thanks to the crash report you provided via Email, we can see that the issue you are encountering is happening behind-the-scenes, and is as follows:

"Unknown column 'ComponentParentID' in 'INSERT INTO'\"

We can also confirm that you are using Specify 6.8.03 and v7.11.0.2 together, which is expected. It seems that this is preventing you from loading the data you can see in Specify 6, but I can confirm the data is still there.

I believe the issue has to do with the Specify 7 installation itself as the database schema migrations seem to have been not completed successfully.

Can you send us a backup of the database so that we can advise on the next steps for resolving this issue? If this is not possible, we can provide guidance on how to troubleshoot the database schema discrepancy together.