hi,

I had no problem during installation (creating and populating database are ok).

Trying to connect to "admin/admin.php" for the first time, I get this 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 '' at line 1ELECT define_questions, edit_survey_property, delete_survey FROM lime_surveys_rights WHERE sid=74 AND uid =



I run limesurvey 1.70+ onto a brand new server:

Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Linux 2.6.18-53.1.14.el5
php-5.1.6-15.el5
php-mysql-5.1.6-15.el5
mysql-server-5.0.22-2.2.el5_1.1
mysql-5.0.22-2.2.el5_1.1

Need help please.

Strange error message. Please re-install the latest release (build 4600). Seems that the database was'nt populated correctly.

Here is the build I 've re-installed :

limesurvey170plus_build4600_20080330.tar


1st step : "Database has been created."
2nd step : "Database `limesurvey` has been successfully populated."
3nd step : Everything is fine - you just forgot to delete or rename
your LimeSurvey installation directory (/admin/install).
Please do so since it may be a security risk."

/limesurvey/admin/admin.php :


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 '' at line 1:
SELECT define_questions, edit_survey_property, delete_survey FROM
lime_surveys_rights WHERE sid=74 AND uid =



Strange ... It sounds like an sql syntax error. Can it be related to mysql version 5.1 ?.


It seems that uid var is not correctely valuated.


If I set uid = 1, in limesurvey/admin/admin.php, I have no more this error,
though it does not work anyway (blank page)


$surquery = "SELECT * FROM {$dbprefix}surveys_rights
WHERE sid=".db_quote($surveyid)." AND uid = 1"
#".db_quote($_SESSION['loginID']); //Getting rights for this survey




Thanks.

Did you completely delete the database before re-installing?

If this doesn't solve the problem please open a ticket at the bugtracker.

Has this been solved now?

Deleting cookies and/or using another browser might solve the problem.

Hello, I also had the same error on a fresh installation. Ends up clearing cookies fixed the issue for me... Thanks for the suggestion!