Specify6 Wizard could not insert StorageTreeDef

I’m trying to use the Specify6.8.03 wizard to create a new database from scratch. Set all the permissions right, go through the whole preparation and then every time get met with this error message:

What gives!?

Well, it turns out I have faced this issue before, but since I don’t do this very often I forgot that one needs to press the one button and not the other:

I look forward to no longer needing Specify6 for this process, because it is very clunky and quite unclear, especially here. Clearly, one wants to test the IT Login to make sure it works, and the phrase “…if you manually created the database” could be taken as having created the empty database, which I did. It’s very unclear it meant “the database and the full structure”. I mean, that is what the wizard is for, right? Who in their right mind would manually create each table for this ever?

Not out of the woods yet, though… :tired_face:

image

Hi @fedoras,

Actually, this is correct. The Test IT Login function allows you to use the Wizard with an entirely blank database as long as you have given the IT User the appropriate permissions.

In the log file you sent via email, I see the following is where it ends:

240130 11:19:40     92 Query    select count(*) from spversion
                    92 Query    INSERT INTO spversion (AppName, AppVersion, SchemaVersion, TimestampCreated, TimestampModified, Version) VALUES('Specify', '6.8.03', '2.10', '2024-01-30 11:19:40', '2024-01-30 11:19:40', 1)

I have never seen the database build process fail at this point before, so I’d like to get a better idea of the installation environment / permissions of the SQL user.

Can you share the permissions of the ituser in MariaDB?

SHOW GRANTS FOR 'ituser'@'localhost';

Can you also share your MariaDB version?

Thank you!

Actually, this is correct. The Test IT Login function allows you to use the Wizard with an entirely blank database as long as you have given the IT User the appropriate permissions.

But then it will not create all the necessary tables and therefore fail on the step where it starts inserting data into StorageTreeDef…

Can you share the permissions of the ituser in MariaDB?

Actually, the screenshot I made was not of the actual process I went through. The real username is ‘situ’ and the host is ‘specifydb01fl’

For some reason, even though I can log in as the user to the database and so can the wizard using it, it states “no such grant defined”. I don’t understand that…

The MariaDB is version 10.3.39… Should I upgrade?

Not specifying the host does give these results:

GRANT RELOAD, CREATE USER ON *.* TO `situ`@`%` IDENTIFIED BY PASSWORD '*84765546CA9517C6D4BD50D31108251F3A9D1864'
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON `Specify`.* TO `situ`@`%` WITH GRANT OPTION
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON `AUH`.* TO `situ`@`%` WITH GRANT OPTION
GRANT SELECT ON `mysql`.* TO `situ`@`%`

The database I’m trying to create is the one called AUH

If you already tried to create a database with the same name, the Test IT Login function will skip the very important step of dropping the existing database and creating a new one. If the database is not empty, it will inevitably fail due to the wizard attempting to insert a duplicate record (duplicate specify username, duplicate tree, etc.).

It is possible that the error is happening at the same place in both instances, the error reporting is just different during the generation process and in the wizard. The error should be logged in the file available at C:\Users\USERNAME\Specify\specify.log and may provide additional insight into the issue.

The MariaDB is version 10.3.39… Should I upgrade?

MariaDB 10.3+ is supported, but internally we are using version 11.2.2. Upgrading would be beneficial in the long run!

I’ve asked a member of our team with SQL expertise to take a closer look later today at this issue! Thank you for your patience and for providing additional information!