Magento2: Error while enabling module via Component Manager (CE 2.1)

[hrle991]

I have downloaded and installed a fresh copy of Magento 2.1 from Magento official website. Then I tried to enable several different modules in admin via 'Web Setup Wizard' --> 'Component manager' but got the same error every time. I tried on several machines with Magento 2.1 installation and the same error always occurs.

Preconditions

1. Magento CE 2.1,0

2. PHP 5.6.24, MySQL 5.6.31

   Steps to reproduce

3. Put module files in [magento_installation]/app/code/[vendor]/[module_name] or do the step no. 3

4. Log into Magento 2.1 admin and go to System -> Web Setup Wizard -> Component Manager
5. Optionally you can sign in with a Magento Marketplace account to sync your bought modules

6. Find your newly added\bought module in modules grid and choose 'Enable' Action

   Expected result

7. Magento should offer you to do a backup and go to a maintenance mode

8. Disable all cache types
9. Enable module
10. Do a setup:upgrade
11. Enable previously disabled cache types
12. Recompile static files
    

    Actual result

1. Magento fails to enable previously disabled cache types and module installation fails:

_An error occurred while executing job "setup:cache:enable ["config layout block_html collections reflection db_ddl eav customer_notification full_page config_integration config_integration_api translate config_webservice"]": Could not complete setup:cache:enable ["config layout block_html collections reflection db_ddl eav customer_notification full_page config_integration config_integration_api translate config_webservice"] successfully: The "command" argument does not exist._

error_log.txt

I have done some error tracing and I believe the problem is in execute() method located in setup\src\Magento\Setup\Model\Cron\JobSetCache.php. If I leave(comment) out IF conditions on line 67 and 70 then Magento manages to do cache:enable and module installation is successful.

[dthampy]

An internal Jira ticket has been created ->MAGETWO-56816.
Thanks for your detailed bug report

[gabriel-sf]

Does anyone have any update on this? or should we try the hack by @hrle991 ?

[dthampy]

This issue has been resolved internally and will be available in a future release.

Thanks.

[mom4751]

Hi,
i have just tried with Magento CE 2.1.1 and the issue is still here.
So the fix has not been implemented yet :-(

[f00stx]

I'm also having this issue, and have recently done an upgrade to CE 2.1.2. Is there a fix for this somewhere? This was a clean install from a version downloaded last week, which I upgraded to 2.1.2 today, and then tried to install an extension via the web setup wizard.

I didn't think to capture the output before closing the tab but it closely matches the output @hrle991 pasted in the ticket.

[bad-for-zathras]

Still present in 2.1.5. It was reported on 3. Jun 2016 (#4853) and again on 9. Aug 2016. No patch landed in the code after 9 months?

[mom4751]

@bad-for-zathras
Since this problem occured, i started to manage Magento 2 with Composer (and i think almost everyone does the same).
I never tried before because i thought it could not work on a shared/managed hosting without root privileges.
I was wrong: you just need an SSH connection.
Now i heavily use Composer to add and remove plugins and upgrade the Magento core too.
I got to the point where i have forgot the web setup wizard existence.

[justanewbie00]

I am using CE 2.1.6 and the problem still exist. I tried to enable the module I created and this error occured. Is there any solution for this?

[drpit]

Hello,
I use CE 2.1.7 and this issue still exist

[magento-engcom-team]

@hrle991, thank you for your report.
The issue is already fixed in 2.1.0, 2.2.0