Read this First

If you have been affected by this, read over the system requirements to be certain the platform on which you are installing meets them.

Original Report

Some unknown system requirement or setting not specified in the requirements is rendering Drupal uninstallable.

Manifests as: Cannot install Drupal, hangs at "Installing Drupal: Initializing"
Initializing
I let it hang all night, tried 5 or 6 times. It managed to created some database entries (screenshot). The only install warning I got was no opcache (due to a recent update config problem), otherwise, I generally run bloated PHP scripts and massive D6/D7 sites on my local all the time and have no problems.

I have marked this as "critical" because, well, it blocks installation. Using minimal install, mariadb.

Here's the output of the error page when I eventually interrupt the process:

Error
The website encountered an unexpected error. Please try again later.
Drupal\Core\Config\UnmetDependenciesException: Configuration objects (block.block.stark_admin, block.block.stark_branding, block.block.stark_local_actions, block.block.stark_local_tasks, block.block.stark_login, block.block.stark_messages, block.block.stark_page_title, block.block.stark_tools) provided by minimal have unmet dependencies in Drupal\Core\Config\UnmetDependenciesException::create() (line 89 of core/lib/Drupal/Core/Config/UnmetDependenciesException.php).

Drupal\Core\Config\UnmetDependenciesException::create('minimal', Array)
Drupal\Core\Config\ConfigInstaller->checkConfigurationToInstall('module', 'minimal')
Drupal\Core\ProxyClass\Config\ConfigInstaller->checkConfigurationToInstall('module', 'minimal')
Drupal\Core\Extension\ModuleInstaller->install(Array, )
Drupal\Core\ProxyClass\Extension\ModuleInstaller->install(Array, )
install_install_profile(Array)
install_run_task(Array, Array)
install_run_tasks(Array)
install_drupal(Object)

Here is my phpinfo(). I'm happy to give any other output, I use a debugger and can give useful debug information.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

glass.dimly created an issue. See original summary.

glass.dimly’s picture

Issue summary: View changes
glass.dimly’s picture

Issue summary: View changes
glass.dimly’s picture

Issue summary: View changes
plach’s picture

Version: 8.0.0-rc1 » 8.0.x-dev
Status: Active » Postponed (maintainer needs more info)

Thanks for reporting this :)

I cannot reproduce the problem with RC1 on MAMP, can you check whether the error is still there with the latest HEAD?

dawehner’s picture

Ideally this exception would say which dependencies aren't met ...

kalpeshhiran’s picture

Can you try changing value of xdebug.max_nesting_level to 300. You can add following configuration in settings.php

ini_set('xdebug.max_nesting_level', 300);

dawehner’s picture

@kalpeshhiran
Interesting point, don't we have requirement checks early running which should validate that?

glass.dimly’s picture

@kalpeshhiran and @dawehner,

There was a requirements check for xdebug.max_nesting_level < 256, and I had increased to 256. Now I've increased to 500.

In the process of checking xdebug.max_nesting_level, I realized that after my latest homebrew PHP recompile, I needed to reinstall php56-xdebug because I wasn't seeing it on phpinfo.

And now Drupal is installing, though it appears to be stuck on 5/40 "Installed Filter Module." I'll have another go and report back here as I learn more.

EDIT: The install is progressing now, albeit sloooowly.

kalpeshhiran’s picture

@dawehner
Yes. As @glass.dimly said there is requirement check for xdebug.max_nesting_level < 256.

@glass.dimly
That's great. Keep this issue posted on the progress.

glass.dimly’s picture

FileSize
37.71 KB

So bad news: I gave it a couple of tries, left it all night, and the install hangs at "Installed text module." My next step will be to try to replicate with the dev branch.

Error
The website encountered an unexpected error. Please try again later.
Drupal\Core\Config\UnmetDependenciesException: Configuration objects (block.block.bartik_account_menu, block.block.bartik_branding, block.block.bartik_breadcrumbs, block.block.bartik_content, block.block.bartik_footer, block.block.bartik_help, block.block.bartik_local_actions, block.block.bartik_local_tasks, block.block.bartik_main_menu, block.block.bartik_messages, block.block.bartik_page_title, block.block.bartik_powered, block.block.bartik_search, block.block.bartik_tools, block.block.classy_page_title, block.block.seven_breadcrumbs, block.block.seven_content, block.block.seven_help, block.block.seven_local_actions, block.block.seven_login, block.block.seven_messages, block.block.seven_page_title, block.block.seven_primary_local_tasks, block.block.seven_secondary_local_tasks, block_content.type.basic, comment.type.comment, contact.form.feedback, core.entity_form_display.node.article.default, core.entity_form_display.node.page.default, core.entity_form_display.user.user.default, core.entity_view_display.node.article.default, core.entity_view_display.node.article.rss, core.entity_view_display.node.article.teaser, core.entity_view_display.node.page.teaser, core.entity_view_display.user.user.compact, core.entity_view_display.user.user.default, editor.editor.basic_html, editor.editor.full_html, field.field.block_content.basic.body, field.field.comment.comment.comment_body, field.field.node.article.body, field.field.node.article.comment, field.field.node.article.field_image, field.field.node.page.body, field.field.user.user.user_picture, field.storage.node.comment, field.storage.node.field_image, field.storage.node.field_tags, field.storage.user.user_picture, filter.format.basic_html, filter.format.full_html, node.type.article, node.type.page, rdf.mapping.comment.comment, rdf.mapping.node.article, rdf.mapping.node.page, rdf.mapping.taxonomy_term.tags, taxonomy.vocabulary.tags) provided by standard have unmet dependencies in Drupal\Core\Config\UnmetDependenciesException::create() (line 89 of core/lib/Drupal/Core/Config/UnmetDependenciesException.php).

Drupal\Core\Config\UnmetDependenciesException::create('standard', Array)
Drupal\Core\Config\ConfigInstaller->checkConfigurationToInstall('module', 'standard')
Drupal\Core\ProxyClass\Config\ConfigInstaller->checkConfigurationToInstall('module', 'standard')
Drupal\Core\Extension\ModuleInstaller->install(Array, )
Drupal\Core\ProxyClass\Extension\ModuleInstaller->install(Array, )
install_install_profile(Array)
install_run_task(Array, Array)
install_run_tasks(Array)
install_drupal(Object)
cilefen’s picture

Priority: Critical » Normal

"Critical" status is only by community consensus. One person unable to install the Drupal 8 RC is not critical. Could you please enable opcache and disable xdebug entirely and try again?

cilefen’s picture

Priority: Normal » Major

Major is ok.

cilefen’s picture

Incidentally, I run with PHP 5.6 on homebrew.

emena’s picture

Hello,

A have the same problem with

PHP 5.5.9-1 on ubuntu4.13 (?)
Apache/2.4.7 (Ubuntu)
Version du client de base de données: libmysql - 5.5.44
I am up to date on ubuntu 14

EM

akhtar2026’s picture

Hello,
i am getting fol error when trying the drupal8 RC on acquia Dev Desktop.
Install does not even started.
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drupal8_rc.router' doesn't exist: SELECT name, route, fit FROM {router} WHERE pattern_outline IN ( :patterns__0 ) AND number_parts >= :count_parts; Array ( [:count_parts] => 0 [:patterns__0] => / ) in Drupal\Core\Routing\RouteProvider->getRoutesByPath() (line 344 of core\lib\Drupal\Core\Routing\RouteProvider.php).

cilefen’s picture

@akhtar2016, @emena If you have xdebug installed, increase xdebug.max_nesting_level as mentioned in #7.

Here is my phpinfo on a working system for comparison.

glass.dimly’s picture

Working with no warning or errors on the requirements page, opcache installed, from the 8x-dev branch, it's hanging at 13%. I will disable xdebug for comparison.

glass.dimly’s picture

Still not working with the zend_extension="/usr/local/opt/php56-xdebug/xdebug.so" stanza in php conf removed. This time no errors, just hanging on initializing.

Maybe this has to do with the fact that I've used --enable-maintainer-zts when I recompiled PHP? This is for pthreads with is required for the redis PHP extension. If I can't work something else out I'll recompile without it.

@cilefen I'll have a look at your phpinfo and have another go soon. I'll also remove all my PHP customizations and see if I can trace it to any one non-stock config stanza.

glass.dimly’s picture

Issue summary: View changes
glass.dimly’s picture

Title: Cannot install Drupal, hangs at "Installing Drupal: Initializing" » Installation requirements do not capure full installability criteria
Issue summary: View changes
cilefen’s picture

@akhtar2026 That's a different issue according to what you posted. Please search the issue queue to see if a matching issue is already opened or create one if necessary. It could be:

It may be necessary to set the system variable max_allowed_packet to at least 16M

-- https://www.drupal.org/requirements/database

emena’s picture

I am sorry,

y try to install xdebug, but something is wrong

I use this help.
If PECL tell me that xdebug is install, it's not were it suppose to be.

I will continue tomorrow and give you my results.
EM

cilefen’s picture

@emena People have disabled xdebug in similar issues, as mentioned in #7.

Has anyone affected checked the the MySQL setting I mentioned in #22?

emena’s picture

Hello,

Sorry, my english is very poor

About SQL, i thing that it's ok

key_buffer		= 16M
max_allowed_packet	= 16M
thread_stack		= 192K
thread_cache_size       = 8
myisam-recover         = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10

If you want some more traces tell me (with basic english)
EM

emena’s picture

Hello,

Do you have any news ?
I still have the problem and i do not find any solution.
Merci d'avance
EL

cilefen’s picture

Title: Installation requirements do not capure full installability criteria » UnmetDependenciesException when installing Drupal 8

This issue is about the UnmetDependenciesException as written in the issue summary. People have reported other installation problems. If you have a different error, search for an existing issue. Open a new issue if necessary.

@emena Are you trying with Drupal 8 RC2?

emena’s picture

YES

I found

This happens when i try a multisite installation.
I tried to do a simple installation, all is well.

cilefen’s picture

How much RAM does PHP have on your system?

emena’s picture

Hello,

I found it necessary to create sites.php as here, I had done wrong.

Do not add any thing, just make a copy.

Thing you for your help
EM

PS, i have 128M memory/

starvagrant’s picture

FileSize
5.27 KB

I've been running into this problem on installation (except that my installation gets stuck during the database setup stage). I've been able to reliably reproduce this error, and have checked my Apache logs. I attempted to install Drupal on Ubuntu 14.04 with firefox 43.0 and chrome 47.0. Observing the access logs, I note that Firefox hangs forever on a 302 redirect and 2 request header timeouts occur in my error logs, whilst Chrome continues (slowly) with the installation. As Firefox appears unresponsive, I press the refresh button and that triggers the exception.

cilefen’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)
dddave’s picture

Status: Closed (works as designed) » Active

Comment #32 was swallowed by Mollom. I've published it and granted starvagrant the community role.

david_garcia’s picture

Related issues: +#2651538: nextId() is broken

There might be several reasons for the error in #11 to happen.

I've been debugging a problem with the SQL Server and the error in #11:

The website encountered an unexpected error. Please try again later.
Drupal\Core\Config\UnmetDependenciesException: Configuration objects (block.block.bartik_account_menu, block.block.bartik_branding, block.block.bartik_breadcrumbs, block.block.bartik_content, .....

This happens when one of the install phases is skipped.

There might be several reasons for this happening, as the step that is skipped is the first one that depends on the BATCH API (install_profile_modules), so anything breaking the batch API will lead to the error.

In SQL Server, the issue was that the nextId() call used to populate que batch ID was returning an initial "0", and this was making the whole step to be skipped due to the usage of loose operators.

Anyways, any other reason that will make the batch part of "install_profile_modules" to be skipped will lead to the error message in #11. For example, the installer store the BATCH id in the current session, so any issues with the session will make this error show up.

Sylvain Lecoy’s picture

Its really not clear which dependency is unmet in the exception

david_garcia’s picture

Its really not clear which dependency is unmet in the exception

Yes that is another issue, unmet dependencies are not collected anywhere, just checked for and reported.

smk-ka’s picture

sanoopuio’s picture

Able to reproduce this error php 5.6 with opcode cache disabled

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

rakesh.gectcr’s picture

FileSize
441.44 KB

Error

cilefen’s picture

@rakesh.gectcr Yes, this exception does not point an admin to the actual cause. Have you made sure to meet the installation requirements?

inkeyes’s picture

I have reported this problem also here: https://www.drupal.org/node/2768427

Are there any workarounds available? or, are there any settings to output more useful debug information as to which installation phases were skipped (as explained above)

Would it be useful if I provided the output from phpinfo() ?

Thanks

cilefen’s picture

Is opcache enabled?
Is xdebug enabled?

inkeyes’s picture

I have enclosed extracts from phpinfo();

PHP Version 5.5.9-1ubuntu4.17
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies, with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies

Opcode Caching Up and Running
Optimization Enabled
Startup OK
Shared memory model mmap
Cache hits 150159

xdebug is not installed

OS Version:
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"

Should I upgrade or move to a server with Ubuntu 16.04?

mpp’s picture

This error also occurs when enabling a module with a block config with a dependency to a (Bartik sub) theme:

 [ERROR] Configuration objects (block.block.my_block) provided by my_module have unmet dependencies

block.block.my_block.yml:

dependencies:
  theme:
    - my_bartik_subtheme

Removing the dependency is a workaround:

dependencies: {}

my_bartik_subtheme is a dependency of my profile so it should be available...

I wonder if checkConfigurationToInstall takes theme dependencies properly into account?

Edit: I seems that the theme is installed last. According to this change record the block (depending on the theme) should be an optional config: https://www.drupal.org/node/2453919

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

bjornhalvorsen@yahoo.com’s picture

I got exactly the same problem when installing Drupal 8.2.0-rc1 on AWS LAMP. Did you find a solution to the problem? Could you please share it here?

le72’s picture

Same problem here.

sosguthorpe’s picture

I had this issue today and it was a Cookie issue. For me I was using mod_header to modify the cookies to have the "secure" and "http only" options. Disabling this has fixed this issue for me and allowed me to complete the install. The behaviour of the install restarting from the beginning points to cookies being at fault.

HongPong’s picture

Using Acquia Dev Desktop with PHP7.0.4 and the current Drupal core version, I ran into this when i tried to install in Safari. When I ran the installer in Chrome it was fine, so I would also suspect cookies. (Also people should clear cache files in sites/default/files/config_xxx ) Thank you sosguthorpe.

Also here https://www.drupal.org/node/2613796 the_new_guy2 dug into the session cookies issue.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Fjsanchez’s picture

I've done this:

"vivekguptakota CreditAttribution: vivekguptakota commented 2 years ago
Added following line in settings.php file and Error fixed.
ini_set('xdebug.max_nesting_level', 300);"

And deleted the MySQL Drupal BD.

Started again the configuration and it worked fine.

It looks like a SQL server problem during BD creation (may be the BD user).

Thanks

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

hiramanpatil’s picture

Getting same error with Drupal version 8.5.6

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

auxiliaryjoel’s picture

I"m getting a similar error when trying to install 8.6.13 currently
is there any way to fix this?

cilefen’s picture

Issue summary: View changes
auxiliaryjoel’s picture

I tried #9 from this thread:
https://www.drupal.org/project/drupal/issues/2558371
it did not fix the issue, the error remains.

However maybe I need to scrap the build/directory entirely and do the #9 fix first, prior to running the installer.
I will try that shortly, but first I will see if any other replies solve the issue...

Some more info before I do that:
I also tried installing via composer in 2 different ways, eg. this way:
composer create-project drupal-composer/drupal-project:8.x-dev mydir --stability dev --no-interaction
and this way:
composer create-project drupal-composer/drupal-project:8.x-dev mydir --no-interaction

but in either case, the same error occurs after the database and install type steps, next step after that displays the issue with no ability to ignore or proceed.

I tried to refresh the install by loading the install path directly:
(example): http://localhost:8888/mydir/web/core/install.php

It did load the installer page, but again after first few steps: add database, choose install type, then the error occurs again.

Next I tried the same thing again, except this time with the settings.php file removed, as per @vlad13's suggestion in #35 here:
https://www.drupal.org/project/drupal/issues/2558371

but that just gives me a page within the installer telling me I need to provide a settings.php file
so I went back to reinstate the settings php, and noticed that the system had already built it's own one...?
so I jumped back to the install browser window and hit refresh,
...and I got the same error again.

@cilefen's comment #33 comment here:
https://www.drupal.org/project/drupal/issues/2558371#comment-13052364
suggested I change max_allowed_packet settings as per the System Requirements documentation here: https://www.drupal.org/docs/8/system-requirements

But when I followed that link and all links it provided, I could not find mention of:
max_allowed_packet
or
packet
anywhere. So not sure how to further that suggestion.

And just to clarify,
I am running this on localhost inside MAMP on Mac,
And in MAMP's htdocs I have 2 previous sites still running OK that both installed fine using the same method
so I'm not sure how this new one could be an issue whilst the other 2 (both made within the last 3months) both installed OK and are running OK.

The fact the other 2 are working alright makes me wonder if the drupal source files that composer reaches for when it runs:
composer create-project drupal-composer/drupal-project:8.x-dev mydir --no-interaction

have changed in some way?

auxiliaryjoel’s picture

In case anyone is still reading this,
@weitzman commented on the github link for composer project, that this recent issue might be the reason:
https://www.drupal.org/project/drupal/issues/3045349

cilefen’s picture

@auxiliaryjoel It is two links deep: database server > common configuration issues

https://www.drupal.org/node/259580

IIRC Mamp ships with a low value. This could be a “red herring”.

auxiliaryjoel’s picture

Sorry cilefen I read your link but not sure if you're saying that this is in relation to this:
https://www.drupal.org/project/drupal/issues/3045349
or something else?

cilefen’s picture

D7 docs were a bit clearer on it https://www.drupal.org/docs/7/system-requirements/database-server

I was not the one to suggest a connection between this and #3045349: Lazy started sessions with session data are not saved with symfony/http-foundation 3.4.24. That was Moshe according to #62. He’s smart—he may be right.

I’ve been consistently talking about a MySQL config that I seem to remember causing this installation issue.

auxiliaryjoel’s picture

Thanks cilefen.
I tried this (in relation to your link: https://www.drupal.org/node/259580):
I went to my MAMP php.ini file:
Applications / MAMP / conf / php7.2.10 / php.ini
and added these lines in:

#MyISAM specifications

[mysqld]
max_allowed_packet = 128M
query_cache_size = 128M

(Neither of the above were already there, so I added them in new)
This is based on suggestions from @code-drupal and @hardik jayeshbhai hihoriya form the link you provided.
I then saved the file, stopped my MYSQL server (in MAMP app) and restarted it again, and then loaded:
http://localhost:8888/mydir/web/core/install.php

which started the installer again, but as soon as I select Language and Install type, the next window went straight to the same error again.

cawi’s picture

I get the following error, when I installed drupal 8 with composer (composer create-project drupal-composer/drupal-project:8.x-dev my_site_name_dir --no-interaction)
It is the first time that I get this error and exactly one week ago erverything worked fine. But I did not change anything.
I am working with MAMP and PHP 7.3.3
@auxiliaryjoel I think it is not a MAMP problem.
I tried to install without composer a drupal 8 project and it is working fine too. So, maybe the question is what changed in composer-files the last week?

Error
The website encountered an unexpected error. Please try again later.
Drupal\Core\Config\UnmetDependenciesException: Configuration objects provided by standard have unmet dependencies: block.block.bartik_account_menu (block), block.block.bartik_help (help, block), block.block.bartik_search (search, block), block_content.type.basic (block_content), comment.type.comment (comment), contact.form.feedback (contact), core.entity_form_display.block_content.basic.default (text), core.entity_form_display.node.article.default (image.style.thumbnail, comment, image, path, text), core.entity_form_display.node.page.default (path, text), core.entity_form_display.user.user.default (image.style.thumbnail, image), core.entity_view_display.node.article.default (image.style.large, comment, image, text), core.entity_view_display.node.article.rss (core.entity_view_mode.node.rss), core.entity_view_display.node.article.teaser (core.entity_view_mode.node.teaser, image.style.medium, image, text), core.entity_view_display.node.page.teaser (core.entity_view_mode.node.teaser, text), editor.editor.basic_html (ckeditor, editor), field.field.block_content.basic.body (field.storage.block_content.body, text, field), field.field.comment.comment.comment_body (field.storage.comment.comment_body, text, field), field.field.node.article.body (field.storage.node.body, text, field), field.field.node.article.comment (comment, field), field.field.node.article.field_image (image, field), field.field.node.article.field_tags (field), field.storage.node.comment (comment, node, field), field.storage.node.field_image (file, image, node, field), field.storage.node.field_tags (node, taxonomy, field), field.storage.user.user_picture (file, image, field), filter.format.basic_html (editor, filter), filter.format.restricted_html (filter), node.type.article (node), rdf.mapping.comment.comment (comment, rdf), rdf.mapping.node.article (node, rdf), rdf.mapping.taxonomy_term.tags (taxonomy, rdf), taxonomy.vocabulary.tags (taxonomy) in Drupal\Core\Config\UnmetDependenciesException::create() (line 98 of core/lib/Drupal/Core/Config/UnmetDependenciesException.php).
Drupal\Core\Config\UnmetDependenciesException::create('standard', Array) (Line: 485)
Drupal\Core\Config\ConfigInstaller->checkConfigurationToInstall('module', 'standard') (Line: 132)
Drupal\Core\ProxyClass\Config\ConfigInstaller->checkConfigurationToInstall('module', 'standard') (Line: 150)
Drupal\Core\Extension\ModuleInstaller->install(Array, ) (Line: 83)
Drupal\Core\ProxyClass\Extension\ModuleInstaller->install(Array, ) (Line: 1663)
install_install_profile(Array) (Line: 709)
install_run_task(Array, Array) (Line: 584)
install_run_tasks(Array, NULL) (Line: 125)
install_drupal(Object) (Line: 44)

Sebbon’s picture

I came here from a duplicate issue. It seems the solution for my problem (not being able to install via the browser and getting 'Unmet dependencies' error like @cawi states above) was:

- create a new project with composer create-project drupal-composer/drupal-project:8.x-dev
- add the conflict line to my composer.json, as stated in https://www.drupal.org/project/drupal/issues/3045349

"conflict": {
"symfony/http-foundation": "3.4.24"
},

- then run 'composer update'
- finally install a new site via the UI

cawi’s picture

@Sebbon Thank you! Now the installation is working.

cilefen’s picture

auxiliaryjoel’s picture

Thank you @Sebbon !

jabberwooki’s picture

Yes, thanks to @Sebbon. Solution #68 works for me as well.

maxdmayhew’s picture

#68 @Sebbon Thank you so much!

This worked for me.

jordanl’s picture

#68 @Sebbon worked here too. Thank you very much!

edit, I can't type. :p

joachim’s picture

Status: Closed (duplicate) » Active

I am still seeing this with 8.7.1, which is using symfony/http-foundation v3.4.27.

I've tried the patch from https://www.drupal.org/project/drupal/issues/3045349#comment-13053689 (which has been committed and then later reverted).

So I'm not sure #3045349: Lazy started sessions with session data are not saved with symfony/http-foundation 3.4.24 is the cause.

jgloverattronedotcom’s picture

I was in the process of building an image in Docker and ran into this issue. One of the dependencies from Composer had recommended to install the uopz PHP extension. The install page would load just fine, but when I clicked to continue after selecting an install profile (already had a settings.php file in place), I got the UnmetDependenciesException error. Removing the uopz PHP extension fixed the issue for me.

Drupal 8.7.3
PHP 7.3

caspervoogt’s picture

I ran into this just now, and for me the fix was simple: I tried installing using a different browser, and it worked fine. So at least some of these cases are due to cookies somehow.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

afagioli’s picture

I fixed today changing database name in settings.php
Broken DB thus.

uotonyh’s picture

Good afternoon,

Attempting to install Drupal 8.9.13 with FireFox 87.0 on macOS Big Sur 11.2.3 running MAMP Pro 6.3, and ran into the 'UnmetDependenciesException'.

Switched over to Safari for the install and install completed successfully.

Thank you.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

webservant316’s picture

#51 helped me find the reason for this problem in my install. My server requires secure cookies and I think this is related to sessions also. Main point is that all my sites need to run on HTTPS because of this if using sessions, cookies, or post. And I was able to install test D9 sites for all my domains, except one. It was maddening that I couldn't see a difference. Well the problem site was running on HTTP and I didn't notice. Once I properly installed the autoSSL for the problem sub-domain then everything installed fine.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Active » Closed (works as designed)
Issue tags: +Bug Smash Initiative

The majority of reports of this happening stopped 3 years ago. There have been 3 since and only one of those is on a supported version of Drupal.

On skimming, the solutions have been varied. From using a different browser to cookies or to changing setttings.php values. If there is (or was) a bug it was never tracked down to a single cause that was a bug in core.

Therefore I am restoring the status set in #33, that this is working as designed.

If you encounter this error message when installing a supported version of Drupal it would be better to create a new issue and refer to this one.

Thanks!