I get this error when I try to install :

Database error in vBulletin 4.2.0:

Invalid SQL:
CREATE TABLE IF NOT EXISTS `glowhostspamomatic_log`(
`date` DATETIME NOT NULL,
`ip` VARCHAR(15) NOT NULL,
`email` VARCHAR(255) NOT NULL,
`username` VARCHAR(255) NOT NULL,
`message` VARCHAR(255) NOT NULL,
`is_blocked` TINYINT NOT NULL DEFAULT "0",
`user_hash` VARCHAR(50) NOT NULL,
`user_id` INT NOT NULL
) TYPE=MyISAM;;

MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 10
Error Number : 1064

Using VB 4.2 MySQL Version : 5.5.24-cll

Any suggestions ?

Change all occurence of

to

in the XML and that will solve the DB Errors.

Database error in vBulletin 4.2.0:

Invalid SQL:
CREATE TABLE IF NOT EXISTS `glowhostspamomatic_remotecache`(
`date` DATETIME NOT NULL,
`field` VARCHAR(20) NOT NULL,
`is_spambot` INT NOT NULL,
`data` VARCHAR(255) NOT NULL
) TYPE=MyISAM;;

MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 6
Error Number : 1064
Request Date : Wednesday, August 8th 2012 @ 03:02:34 PM
Error Date : Wednesday, August 8th 2012 @ 03:02:34 PM

IP Address : 94.59.232.82
Username : pendu
Classname : vB_Database
MySQL Version : 5.5.24-cll

i have same problem ,, i change this code to xml file

but same problem

You have missed some

missed from where .. that xml file .

can u tell me how to get stopforumspam key ..

U will find a link in the settings near where u input the key

Another member said that you can change the "TYPE=MyISAM", to "ENGINE=MyISAM" but I just removed the items. It shows up 3 times. If you want to see the link where I first made the correction it is located here: https://vborg.vbsupport.ru/showpost....postcount=1639

It's really clear as I have highlighted in RED the 3 places to make changes.

Would rather not remove better to just change them. Don't understand why some are having this problem in the first place

When I first had the problem I did a little research to find that the newer versions of MySQL had tighter security and did not support some of the older commands.

By reading this information again, I guess I could have changed it to ENGINE instead of TYPE, but I didn't. The mod works so that is all I need! The problem is many people do not understand how to track down the errors they receive in the database. But regardless of that we still have some people that just don't bother to read! There are a lot of little steps in setting this mod up and people just want to install and it run 100% without even looking in the AdminCP!