cannot login to a new installation

I’ve installed SuiteCRM on my development machine. after a few problems I got it to install and set up the tables in MySQL. however I cannot login using the logins setup initially. The user table has no records. does anyone have ideas as to how to proceed from here.
regards
Ralph

Hi, welcome.

Please give us some information about your system: SuiteCRM version, PHP version, which OS is it, is it your own server or a shared hosting?

the installation is on my local windows 10 machine. PHP 7.1 SuiteCRM 7.11.5 DB MySQL What happened was I ran install.php This installed but said there was an error creating a table
CREATE TABLE users_feeds (user_id varchar(36) NULL ,feed_id varchar(36) NULL ,rank int NULL ,date_modified datetime NULL ,deleted bool DEFAULT ‘0’ NULL , KEY idx_ud_user_id (user_id, feed_id)) CHARACTER SET utf8 COLLATE utf8_general_ci: MySQL error 1064: 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 'rank int NULL ,date_modified datetime NULL ,deleted bool DEFAULT ‘0’ NULL , ’ at line 1
the error appears to be caused because rank is a reserved word I changed it to ranks and then the query ran and after that changed the field name back to rank.

There are no users listed in the user table. I cannot login with the admin password i set up. I suspect that the installation stopped after the error and the user was never created.
thanks Ralph

I Have since discovered on GITHub
"It seems that rank is an SQL reserved word since MySQL 8.0.2:
https://dev.mysql.com/doc/refman/8.0/en/keywords.html

And we’re using it as a field name here:
https://github.com/salesagility/SuiteCRM/blob/master/metadata/user_feedsMetaData.php#L46

From my search, that is the only reference to that field, so it seems not be used at all after the initial table creation. But I might be missing something."

is there a work around or and updated version of the installer

Oh, so you’re using an unsupported version of MySQL.

I opened an issue for this a few months ago:

https://github.com/salesagility/SuiteCRM/issues/6046

Maybe try the proposed fix there, or wait for this to be released, or downgrade MySQL to a supported version: https://docs.suitecrm.com/admin/compatibility-matrix/