Search code examples
phpdrupaldrupal-8drush

Command cim was not found. Drush was unable to query the database

When running drush cim commands in Drupal 8 I get the following error:

Command cim was not found. Drush was unable to query the database. As a result, many commands are unavailable. 
Re-run your command with --debug to see relevant log messages.

and when I run the drush cim --debug show the following:

$ drush cim --debug
 [preflight] Redispatch to site-local Drush: C:\xampp\htdocs\executive-coatings\docroot/vendor/drush/drush/drush.
 [preflight] Config paths: C:/xampp/htdocs/executive-coatings/docroot/vendor/drush/drush/drush.yml
 [preflight] Alias paths: C:/xampp/htdocs/executive-coatings/docroot/drush/sites,C:/xampp/htdocs/executive-coatings/drush/sites,C:/xampp/htdocs/executive-coatings/docroot/drush/sites
 [preflight] Commandfile search paths: C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\src
 [debug] Bootstrap further to find cim [0.27 sec, 6.78 MB]
 [debug] Trying to bootstrap as far as we can [0.27 sec, 6.78 MB]
 [bootstrap] Drush bootstrap phase: bootstrapDrupalRoot() [0.27 sec, 6.78 MB]
 [bootstrap] Change working directory to C:\xampp\htdocs\executive-coatings\docroot [0.27 sec, 6.78 MB]
 [bootstrap] Initialized Drupal 8.6.13 root directory at C:\xampp\htdocs\executive-coatings\docroot [0.28 sec, 6.9 MB]
 [bootstrap] Drush bootstrap phase: bootstrapDrupalSite() [0.28 sec, 7.15 MB]
 [bootstrap] Initialized Drupal site default at sites/default [0.29 sec, 7.37 MB]
 [debug] Could not find a Drupal settings.php file at sites/default/settings.php. [0.29 sec, 7.37 MB]
 [bootstrap] Drush bootstrap phase: bootstrapDrupalConfiguration() [0.29 sec, 7.37 MB]
 [debug] Add service modifier [0.29 sec, 7.51 MB]
 [bootstrap] Unable to connect to database. More information may be available by running `drush status`. This may occur when Drush is trying to bootstrap a site that has not been installed or does not have a configured database. In this case you can select another site with a working database setup by specifying the URI to use with the --uri parameter on the command line. See `drush topic docs-aliases` for details. [0.29 sec, 7.51 MB]
 [debug] Bootstrap phase bootstrapDrupalDatabase() failed to validate; continuing at bootstrapDrupalConfiguration() [0.29 sec, 7.51 MB]
 [debug] Done with bootstrap max in Application::find(): trying to find cim again. [0.29 sec, 7.51 MB]

In Application.php line 239:

  [Symfony\Component\Console\Exception\CommandNotFoundException]
  Command cim was not found. Drush was unable to query the database. As a result, many commands are unavailable. Re-r
  un your command with --debug to see relevant log messages.


Exception trace:
 () at C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\src\Application.php:239
 Drush\Application->bootstrapAndFind() at C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\src\Application.php:192
 Drush\Application->find() at C:\xampp\htdocs\executive-coatings\docroot\vendor\symfony\console\Application.php:236
 Symfony\Component\Console\Application->doRun() at C:\xampp\htdocs\executive-coatings\docroot\vendor\symfony\console\Application.php:148
 Symfony\Component\Console\Application->run() at C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\src\Runtime\Runtime.php:118
 Drush\Runtime\Runtime->doRun() at C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\src\Runtime\Runtime.php:49
 Drush\Runtime\Runtime->run() at C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\drush.php:72
 require() at C:\xampp\htdocs\executive-coatings\docroot\vendor\drush\drush\drush:4
Solution

  • Please take the following step into consideration as it has the potential to address your problems.

    1. Clear Drush Cache: Clearing the Drush cache may help resolve the issue with drush cache-clear drush
    2. Verify that the config module is enabled in your Drupal installation drush pm:list --type=module | grep config and If the config module is not listed, you can enable it using the following command: drush pm:enable config
    3. you can try running the command with the --debug option to get more detailed log messages. This can provide additional information about the issue and help in troubleshooting.