Encounter MySQL error when installing

New Member Joined: Jan 11, 2006 Posts: 1

Hi,

I had downloaded the new RavenNuke76 v2.02.00 FULL distro pack and tried to do a full installation using the instructions in the QUICKINSTALL guild.

When I was doing step 1 in installSQL.php, I the following error was reported at the bottom of the page.

------------------------------------------------
ERROR! The exact error message that your MySQL server reported is You have an error in your SQL syntax near '; ' at line 1.
------------------------------------------------

I had tried to redownload the package again and upload it but still got teh same error. Anyone able to help on this?

registered · Posted: Wed Jan 11, 2006 9:18 pm

riftmage, I would try to FTP the installSQL.php script file again. It sounds to me like maybe it is corrupted? Try forcing your FTP client to use ASCII on the upload and see if that fixes it. I am thinking there may be ^M characters on each line of the file due to the FTP being set to binary.

Worker Joined: Feb 18, 2004 Posts: 244

I'm having the same problem...

Quote:

ERROR! The exact error message that your MySQL server reported is You have an error in your SQL syntax near '; ' at line 1.

Immediately after pressing Install core files that error appears at the bottom of the page.

RN 7.6/2.0, unix, mysql...

I have reuploaded, forcing ASCII with no change...

The top of the page reports that it can connect to the database.

Quote:

MySQL Database Connectivity Test Results

config.php file found!
Successfully connected to localhost as user test and assigned password!

Raven, could this be that non stardard characters in a db name?? Not being enclosed in back ticks??

Thanks,
Darrell

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

All tables are enclosed in back ticks. What version of MySQL are you using? It sounds like your version is not handling comments that start with -- .

Posted: Fri Jan 13, 2006 6:33 am

Database: MySQL 3.23.58

-----

Server OS: Linux 2.4.20-13.9ensim.smp-3.5.0-14

HTTP Server: Apache/1.3.31 (Unix) (Red-Hat/Linux) mod_jk/1.2.1-beta-1 mod_perl/1.29 PHP/4.3.8 FrontPage/5.0.2.2635 mod_ssl/2.8.18 OpenSSL/0.9.7a mod_fastcgi/2.4.0

PHP Version: 4.3.8 (Zend: 1.3.0)

-----

So if this is the case, what search and replace strings would clear them all out??

Thanks,
Darrell

Posted: Fri Jan 13, 2006 8:42 am

Oh - My - Goodness, is all I can say about your host. I thought I had added all the code to get rid of the comments for all releases but I'd better go back over it again.

Try changing all -- (Note the space after the -- ) at the beginning of a line to ## (Again, there is a space after the ## ).

Posted: Fri Jan 13, 2006 11:06 am

I changed all of (-- ) to (## ) and that still left a few of just (--) so I even changed them to old style comments too. (##)

But, that only changed the install error to this.

Quote:

ERROR! The exact error message that your MySQL server reported is Query was empty.

Posted: Fri Jan 13, 2006 11:14 am

Looks like you deleted something extra. The query wasn't recognized.

Posted: Fri Jan 13, 2006 12:03 pm

Well...

I went back to the original .sql file (rn76_core_pl31.SQL) and tried to import it via phpMyAdmin.

This is the error I got doing that:

Quote:

Error

SQL-query :

CREATE TABLE `nuke_subscriptions` (

`id` int( 10 ) NOT NULL AUTO_INCREMENT ,
`userid` int( 10 ) default '0',
`subscription_expire` varchar( 50 ) NOT NULL default '',
PRIMARY KEY `id` ( `id` , `userid` )
) TYPE = MYISAM

MySQL said:

#1171 - All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead

It's not the same error reported back through your installer script.. Totall different, but same file...

Darrell

Posted: Fri Jan 13, 2006 1:26 pm

What version of phpMyAdmin are you using? I think you are using really old versions of everything. Seriously, consider a new host. The versions of software that you are running are still prone to exploits that have been fixed in the later releases.

Posted: Fri Jan 13, 2006 1:33 pm

It's 2.5.6.

Posted: Fri Jan 13, 2006 1:34 pm

You need, at the very minimum, to get your MySQL and phpMyAdmin up to date.

Hangin' Around Joined: Oct 25, 2003 Posts: 27

I got the same problem on the install, so I tried just using the sql file and doing it manually but guess I can't do that. Has there been any fix as of yet as am not sure what -- or ## means. Your help would be appreciated.

Darlene

New Member Joined: Nov 15, 2005 Posts: 14

Ok I am getting the same problem so I tried installing the sql file in phpmyadmin.

This is the messages I get when installing from phpmyadmin:

SQL query:

CREATE TABLE `nuke_subscriptions` (

`id` int( 10 ) NOT NULL AUTO_INCREMENT ,
`userid` int( 10 ) default '0',
`subscription_expire` varchar( 50 ) NOT NULL default '',
PRIMARY KEY `id` ( `id` , `userid` )
) TYPE = MYISAM

MySQL said:

#1171 - All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead

My version of phpMyAdmin is 2.6.3-pl1

My version of MySQL is 3.23.58

Posted: Fri Jan 13, 2006 4:27 pm

Ravens newer versions of software are exporting .sql files that our older versions of software can't import guys...

Posted: Fri Jan 13, 2006 5:02 pm

Ok I changed this:

Code:

--


-- Table structure for table `nuke_subscriptions`


--





DROP TABLE IF EXISTS `nuke_subscriptions`;


CREATE TABLE `nuke_subscriptions` ( `id` int(10) NOT NULL auto_increment, `userid` int(10) default '0', `subscription_expire` varchar(50) NOT NULL default '', PRIMARY KEY `id` (`id`,`userid`) ) TYPE=MyISAM;








--


-- Dumping data for table `nuke_subscriptions`


--

to:

Code:

--


-- Table structure for table `nuke_subscriptions`


--





DROP TABLE IF EXISTS `nuke_subscriptions`;


CREATE TABLE `nuke_subscriptions` ( `id` int(10) NOT NULL auto_increment, `userid` int(10) default '0', `subscription_expire` varchar(50) NOT NULL default '',  KEY `id` (`id`,`userid`) ) TYPE=MyISAM;








--


-- Dumping data for table `nuke_subscriptions`


--





and





change -- to #

Then install the sql file with phpmyadmin and it work.

Is this ok

Posted: Fri Jan 13, 2006 7:15 pm

A better fix would be to change `userid` int(10) default '0' to `userid` int(10) default '0' NOT NULL