We recently purchased software that runs as an extension for Magento 2. We purchased a brand new VPS setup, and turned it over to them for installation. They completed the installation and got their product working, and turned the site/server back over to us, and everything seemed to be working fine.

I've been attempting to install some additional extensions through Magento's web component wizard, and kept getting the following error at the Cron readiness check:

Cron script readiness check failed.

Error from Updater Application Cron Script:
Cron job has not been configured yet

We configured the Cron Tasks and attempted to run them with bin/magento cron:run but then recieve the following error:

Invalid Document 
Element 'type': Character content other than whitespace is not allowed because the content type is 'element-only'

The same error is also generated when attempting to run magento setup:upgrade

setup:upgrade trace

I'm fairly new to the Magento platform, and am in the dark as to exactly how everything was configured during installation since a third party installed it, so my question is how do I go about tracking down the source of this error? I've looked through just about every log I can find and can't seem to find it.

XML that has been modified/added:

<?xml version="1.0"?>
  • Please delete var/generation & run command again
    – Jackson
    Feb 7, 2017 at 3:14
  • @AnkitShah remove the entire directory, or just delete the files within it?
    – codestr
    Feb 7, 2017 at 3:15
  • @AnkitShah Also, it appears there are two var/generation directories, var/generation and var/generation1
    – codestr
    Feb 7, 2017 at 3:16
  • It should be only one var/generation directory delete other directory
    – Jackson
    Feb 7, 2017 at 3:21
  • So, delete both of them, or delete the second directory and empty the first one?
    – codestr
    Feb 7, 2017 at 3:21

1 Answer 1


Turns out this was an issue with the custom module we had purchased, and was a result of an error in their di.xml file.

  • 2
    Could you please specify the error and how they solved it? Im having the same situation, but no di.xml, other XML seem okay..
    – Max
    Nov 6, 2017 at 20:56
  • @Max So, I'm not 100% sure whether it was maybe a syntax issue, or maybe even an encoding issue, but when I had opened their di.xml file, character spacing was all over the place, random line breaks, etc. All I did was clean up the spacing and re-save the file and the issue disappeared.
    – codestr
    Nov 28, 2017 at 15:26
  • I am facing similar issue and beautified all the XML files of third part module. Still I get the same error. How do I resolve this ? Dec 11, 2017 at 11:08
  • @Vikram have you tried disabling/removing the extension to confirm that it is indeed the cause of the error? It may not be a syntax issue at all, there could be a number of issues wrong, referencing the wrong element, spelling typo, etc.
    – codestr
    Dec 12, 2017 at 14:26
  • @codestr yes the issue is happening when I install a third party extension. If I uninstall, it do not give the exception. How do I resolve this ? Dec 13, 2017 at 5:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.