Well, hmmm. While Google implies this is normally a permissions issue, I also had trouble using the supplied SQL commands to insert data into the table on my own server (tested just now).
So I took a look at it. I visited the database and hit SQL to create the table first -
Code:
CREATE TABLE `adopts_alchemy_settings` (asid INT NOT NULL AUTO_INCREMENT PRIMARY KEY, name varchar(20), value varchar(40))
Then went into the table and hit SQL again to insert the data there -
Code:
INSERT INTO `adopts_alchemy_settings` (`asid`, `name`, `value`) VALUES (1, 'system', 'enabled'), (2, 'chance', 'enabled'), (3, 'recipe', 'enabled'), (4, 'cost', '500'), (5, 'license', ''), (6, 'usergroup', 'all')
I changed the formatting only slightly? And it seemed to help. But the order of operations I think is what really helped, rather than doing it all from the front of the database - to do it while already visiting the table. Try that with the others, too?