Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When trying to upgrade Drupal 8.01 fresh installation from Drupal 7.41 I am getting this error "Source database does not contain a recognizable Drupal version."
Any suggestions?
Yours, Hawk
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | system.pdf | 364.57 KB | findart |
Comments
Comment #2
Hawk_Wala commentedComment #3
mikeryanTo check that the source database is a valid Drupal database, and to determine the version of the database, the upgrade process looks at the 'system' table - is that table present in the database you specified in the form? Is the Drupal installation in that database prefixed (and if so, did you enter the prefix in the "Advanced options" section of the form)?
Comment #4
Hawk_Wala commentedThank you for pointing out reason for the error. Providing tables' prefix solved the issue.
Yours,
Hawk
Comment #5
mikeryanComment #6
Benia commentedI am sorry to say that for me, providing the prefix of the D7 site's tables didn't solve the issue. All of the tables of the D7 site have the prefix 4bn; Trying to click "Review upgrade" with or without it didn't solve the issue... Any help?
Comment #7
Benia commentedReferencing to here from another thread:
This happened to me when I had above-core ("Contrib") modules installed. For those who don't know, usually such modules don't have a migration-path or a patch that will allow them to be part of the Migrate-upgrade process).
It happened to me back in the era when I was very new to this and didn't know that generally nothing which is not core, has a migration-path that comes with the core migration suite. Thus only when I enabled all (or most of all) contrib-modules, I no longer had that problem.
Comment #8
findart commentedI don't have a prefix in my tables and my database is not recognized!
Unfortunately I do not fully understand your answer, do I have to activate all modules that are activated in the core and remove all of them on the database where "0" is shown?
Help
Comment #9
findart commentedI don't have a prefix in my tables and my database is not recognized!
Unfortunately I do not fully understand your answer, do I have to activate all modules that are activated in the core and remove all of them on the database where "0" is shown?
Help
Comment #10
Hawk_Wala commentedCheck the database that drupal has created and compare the table names in the new datebase with those is the original database. If the old database had "dr_" or some other prefixes then the new table must have the same prefixes.
-- Hawk
Comment #11
findart commentedNo prefixes are used in the old and new databases. Are the same!
The only thing I noticed is that the tables utf8_general_ci are used on the old D6 database and utf8mb4_0900_ai_ci on the new D8!
Can that be the mistake?
Comment #12
avpaderno