Magento2: 2.1.0 EE installation fails

[mvillard]

Steps to reproduce

Install Magento EE 2.1.0 with sample data from downloaded ZIP file - Windows 10 - Wamp
PHP 5.6.16

Apache 2.4.17

Error is step 6
Completion 51 %:

Module 'Magento_Cms':
Installing data...

[wert2all]

Please report this issue in partner portal.

[katmoon]

Does anybody know how to fix this issue? I also experience it.

[katmoon]

$ mysql -u root -e "SET GLOBAL FOREIGN_KEY_CHECKS=0; fixes it

[navarr]

@katmoon That's a workaround - but not a solution. We also had this issue and have a ticket in partner portal.

[katmoon]

There is internal ticket MAGETWO-55201 to fix this issue.

[dchaykas]

Any update on this issue? Still getting it while installing today.

[IgorVitol]

Hi! Tried to install Magento 2.1.2 EE and had the same issue.
Spent few hours on debugging this - by some reason all "sequence_" tables was created with "MyISAM" engine - http://prntscr.com/db1ret

Workaround for now:

1. Wait until error occurs. Do not close install window.
2. Go and change engine to InnoDB for all "sequence_" tables.
3. Empty/truncate (or just delete all records) from theese tables.
4. Click - "Try again" in install window.

[dchaykas]

Interesting, I did the workaround of turning foreign key check off and then on again. They should really fix the issue.

[navarr]

We've done the foreign key check but down the road had foreign key issues.

That workaround should not be used

[IgorVitol]

I did the workaround of turning foreign key check off and then on again. They should really fix the issue.

This will solve installation issues. But I beleive that if you will re-enable foreign key checks after install, you will be unable to add any entities (products, categories, e.t.c.).

That's because sequence tables has MyISAM engine, which didn't support foreign keys. Correct fix for that issue would be to set InnoDB engine while creating these tables.

[navarr]

This issue unbelievably still exists in Magento 2.1.4 EE

I've recreated it in MySQL 5.6.35

[navarr]

For those still subscribed to this issue, we may have found the culprit.

We did three things: upgrade to MySQL 5.7 (unlikely to be necessary)

Updated the MySQL open_files_limit configuration. The default for us was 5,000 and our hosting provider upped it all the way to 65,535. If you're having issues with this, I'd recommend seeing if doubling open_files_limit results in success.

If that doesn't work, the other thing that our provider did is changed our max_allowed_packet to "32M".

[IgorVitol]

This issue related to:
MagentoFrameworkDBDdlSequence::getCreateSequenceDdl

As you can see, sql statement for CREATE TABLE is without specified InnoDB engine, which is required for foreign keys. On most Windows mysql servers, it is set to MyISAM by default, so tables will be created incorectly and is the reason for such error. Adding engine to this statement fixed my issue and Magento EE installed without any issues.

[csned]

I've resolved this issue. I'll merge in the fix, which is to ensure that calls to save() come after startSetup(), which disabled FK checks.