Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

Kenneth Brill — Thu, 01 Jul 2021 15:30:14 GMT

Please accept the answer, I'm trying to increase my score a few points

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

James Kinnersley — Thu, 01 Jul 2021 14:48:28 GMT

Kenneth, thank you so much! The installation completed and tables are created, just need to fix the licence validation now but, again, thank you.

James

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

Kenneth Brill — Thu, 01 Jul 2021 14:08:57 GMT

I would guess that this line is your problem,

default-storage-engine=MYISAM

it should be

default-storage-engine=InnoDb

You might also try

innodb_large_prefix = 1

in there too. But hte default engine is the source of the issue.

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

James Kinnersley — Thu, 01 Jul 2021 07:58:37 GMT

Hi Kenneth, thanks for responding. The my.ini is below.

; Example MySQL config file for medium systems.
;
; This is for a large system with memory of 1G-2G where the system runs mainly
; MySQL.
;
; MySQL programs look for option files in a set of
; locations which depend on the deployment platform.
; You can copy this option file to one of those
; locations. For information about these locations, see:
; dev.mysql.com/.../option-files.html
;
; In this file, you can use all long options that a program supports.
; If you want to know which options a program supports, run the program
; with the "--help" option.

; The following options will be passed to all MySQL clients
[client]
;password = your_password
port =3306
socket = /tmp/mysql.sock

; Here follows entries for some specific programs

; The MySQL server
[wampmysqld64]
;skip-grant-tables
default_authentication_plugin=mysql_native_password
port =3306
socket = /tmp/mysql.sock
key_buffer_size = 256M
max_allowed_packet = 1M

;Added to reduce memory used (minimum is 400)
table_definition_cache = 600

sort_buffer_size = 2M
net_buffer_length = 8K
read_buffer_size = 2M
read_rnd_buffer_size = 2M
myisam_sort_buffer_size = 64M
;Path to mysql install directory
basedir="c:/wamp64/bin/mysql/mysql5.7.31"
log-error="c:/wamp64/logs/mysql.log"
;Verbosity Value 1 Errors only, 2 Errors and warnings , 3 Errors, warnings, and notes
log_error_verbosity=2
;Path to data directory
datadir="c:/wamp64/bin/mysql/mysql5.7.31/data"

;Path to the language
;See Documentation:
; dev.mysql.com/.../error-message-language.html
lc-messages-dir="c:/wamp64/bin/mysql/mysql5.7.31/share"
lc-messages=en_US

; The default storage engine that will be used when create new tables
default-storage-engine=MYISAM
; New for MySQL 5.6 default_tmp_storage_engine if skip-innodb enable
; default_tmp_storage_engine=MYISAM

;To avoid warning messages
secure_file_priv="c:/wamp64/tmp"
skip-ssl

explicit_defaults_for_timestamp=true

; Set the SQL mode to strict
;sql-mode=""
sql-mode="STRICT_ALL_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER"

; Don't listen on a TCP/IP port at all. This can be a security enhancement,
; if all processes that need to connect to mysqld run on the same host.
; All interaction with mysqld must be made via Unix sockets or named pipes.
; Note that using this option without enabling named pipes on Windows
; (via the "enable-named-pipe" option) will render mysqld useless!
;
;skip-networking

; Disable Federated by default
skip-federated

; Replication Master Server (default)
; binary logging is required for replication
;log-bin=mysql-bin

; binary logging format - mixed recommended
;binlog_format=mixed

; required unique id between 1 and 2^32 - 1
; defaults to 1 if master-host is not set
; but will not function as a master if omitted
server-id = 1

; Replication Slave (comment out master section to use this)

; New for MySQL 5.6 if no slave
skip-slave-start

;
; To configure this host as a replication slave, you can choose between
; two methods :
;
; 1) Use the CHANGE MASTER TO command (fully described in our manual) -
; the syntax is:
;
; CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
; MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
;
; where you replace <host>, <user>, <password> by quoted strings and
; <port> by the master's port number (3306 by default).
;
; Example:
;
; CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
; MASTER_USER='joe', MASTER_PASSWORD='secret';
;
; OR
;
; 2) Set the variables below. However, in case you choose this method, then
; start replication for the first time (even unsuccessfully, for example
; if you mistyped the password in master-password and the slave fails to
; connect), the slave will create a master.info file, and any later
; change in this file to the variables' values below will be ignored and
; overridden by the content of the master.info file, unless you shutdown
; the slave server, delete master.info and restart the slaver server.
; For that reason, you may want to leave the lines below untouched
; (commented) and instead use CHANGE MASTER TO (see above)
;
; required unique id between 2 and 2^32 - 1
; (and different from the master)
; defaults to 2 if master-host is set
; but will not function as a slave if omitted
;server-id = 2
;
; The replication master for this slave - required
;master-host = <hostname>
;
; The username the slave will use for authentication when connecting
; to the master - required
;master-user = <username>
;
; The password the slave will authenticate with when connecting to
; the master - required
;master-password = <password>
;
; The port the master is listening on.
; optional - defaults to 3306
;master-port = <port>
;
; binary logging - not required for slaves, but recommended
;log-bin=mysql-bin

; Point the following paths to different dedicated disks
;tmpdir = /tmp/
;log-update = /path-to-dedicated-directory/hostname

; The InnoDB tablespace encryption feature relies on the keyring_file
; plugin for encryption key management, and the keyring_file plugin
; must be loaded prior to storage engine initialization to facilitate
; InnoDB recovery for encrypted tables. If you do not want to load the
; keyring_file plugin at server startup, specify an empty string.
early-plugin-load=""

;innodb_data_home_dir = C:/mysql/data/
innodb_data_file_path = ibdata1:12M:autoextend
;innodb_log_group_home_dir = C:/mysql/data/
;innodb_log_arch_dir = C:/mysql/data/
; You can set .._buffer_pool_size up to 50 - 80 %
; of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 256M
; Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
innodb_flush_method=normal

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
; Remove the next comment character if you are not familiar with SQL
;safe-updates

[isamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer_size = 2M
write_buffer_size = 2M

[myisamchk]
key_buffer_size = 20M
sort_buffer_size_size = 20M
read_buffer_size = 2M
write_buffer_size = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld]
default_authentication_plugin=mysql_native_password
port =3306

Thanks again

James

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

Kenneth Brill — Thu, 01 Jul 2021 02:39:23 GMT

OK, I know I had this exact same problem when I loaded v10. But that was a while ago and I cant remember how I solved it. I do know that I have loaded lots of v10+ instances on XAMPP which has a windows version. It seems to me that the problem came down to some settings in mySQL. A google search makes it seem like the issue was in myISAM vs InnoDB tables but I dont think that was my problem.

Can you post your my.ini (or whatever windows uses for a MySQL config file)?

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

James Kinnersley — Wed, 30 Jun 2021 13:13:59 GMT

Hi. I've tried this again with the a new full release copy of Sugar 11 which was provided by support as suggested by Francesca but have had the same result, if anyone who uses WAMP can point me in the right direction to get a local version running, I'd really appreciate it.

The sugarcrm.log file is:-

Wed Jun 30 13:10:01 2021 [13520][-none-][ALERT] Error creating table: acl_actions: Query Failed: CREATE TABLE acl_actions (id char(36) NOT NULL ,date_entered datetime NULL ,date_modified datetime NULL ,modified_user_id char(36) NULL ,created_by char(36) NULL ,name varchar(150) NULL ,category varchar(100) NULL ,acltype varchar(100) NULL ,aclaccess int(3) NULL ,deleted bool DEFAULT 0 NULL , PRIMARY KEY (id), KEY idx_aclaction_id_del (id, deleted), KEY idx_category_name (category, name), KEY idx_del_category_name (deleted, category, name), KEY idx_del_category_name_acltype_aclaccess (deleted, category, name, acltype, aclaccess)) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci: MySQL error 1071: Specified key was too long; max key length is 1000 bytes
Wed Jun 30 13:10:01 2021 [13520][-none-][FATAL] died with message: Database failure. Please refer to sugarcrm.log for details.

Thanks again

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

James Kinnersley — Fri, 25 Jun 2021 14:38:13 GMT

Hi Francesca. Thank you for your response.

I've been using the 10.3 developer version with Vagrant, I picked the latest developer version to download and attempt the WAMP install with essentially to match our cloud version number.

The reason I'm trying to use a developer release is because the full version isn't listed for me in the downloads on the support site, I've logged a ticket with support about this.

I was using PHP 7.3.21, MySQL 5.7.31, Apache 2.4.46, Elasticsearch 7.13.2. which I believe met the requirements. I've since updated WAMP to the latest version and tried again with MySQL 8.0.25 but still had the same "Database failure" message at the end of the install. In both cases sugarcrm database is created, its just empty.

RE: Database failure creating local sugar with WAMP and SugarEnt-11.0.0-dev.1.zip

Francesca Shiekh — Fri, 25 Jun 2021 12:54:18 GMT

I would take a step back, is there a particular reason you are using the developer release of Sugar 11 instead of the full release which is now available?

In general the .dev versions are pre-releases for developers to prepare for upgrades, but you can't upgrade any further from those releases. I would recommend using the latest general release for your development instance, and only using dev releases for future-release testing.

As for the error, I am not sure why the table would be missing, but I would start with reviewing the requirements and making sure your installation meets them, perhaps if you MySQL is not the right version you are missing something the steps that create the database:

support.sugarcrm.com/.../