PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.uuid' in 'field list': SELECT base.tid AS tid, base.vid AS vid, base.name AS name, base.description AS description, base.format AS format, base.weight AS weight, base.uuid AS uuid, v.machine_name AS vocabulary_machine_name FROM {taxonomy_term_data} base INNER JOIN {taxonomy_vocabulary} v ON base.vid = v.vid WHERE (base.tid IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => 1 ) in DrupalDefaultEntityController->load() (line 196 of /Users/hartmut/Sites/mywebsite/includes/entity.inc).

Any hint how to work around it?

Comments

rory_o’s picture

Also having this issue updating to the Aug-21 version. Drupal is unable to bootstrap now. This happened during the UUID module update

Backups were saved into the directory /Users/admin/drush-backups/ppc_drupal/20110822203703/modules/uuid.                   [ok]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5-' for key 'PRIMARY'                               [error]

(stealth sub)

rory_o’s picture

Priority: Major » Critical
rory_o’s picture

Even after disabling UUID in the database by altering the system table and removing the uuid module from the modules directory, Drupal is still unable to bootstrap. It is trying to find the UUID columns which don't exist, and looking at my previous table backups didn't exist before. I don't know why Drupal is trying to find the *.uuid columns now, I would expect it wouldn't after disabling UUID.

It looks like to get it working we need to create the uuid columns, the easiest way to do that would be to uuid_install I would think, but we're stuck in a situation where Drupal won't even bootstrap now. Any advice?

rory_o’s picture

Title: After running DB update for UUID » Drupal unable to bootstrap after running DB update for UUID
skwashd’s picture

Assigned: Unassigned » dixon_
Priority: Critical » Normal
Status: Active » Postponed

As per the relnotes, there is no upgrade path from any previous version to alpha 2, this will be fixed in alpha 3.

duntuk’s picture

same issue here...

chriz001’s picture

me too... anything we can do to fix this for our sites till alpha 3 comes out?

skwashd’s picture

@chriz001 restore from backup and wait.

retrakker’s picture

Went back to alpha1. However, the backup doesn't restore the table AFAICS.

Honza Pobořil’s picture

subscribe

supakitk’s picture

subscribe

supakitk’s picture

I'm disable the module and clear the cache_bootstrap table as temporary fixed.

update system set status=0 where filename ='sites/all/modules/uuid/uuid.module';
truncate table cache;
truncate table cache_bootstrap;
retrakker’s picture

Can confirm that supakitk quick fix gets at least Drupal back on its feet.

http://drupal.org/node/1256888#comment-4897834

Thanks!

sonar_un’s picture

subscribe

danielb’s picture

subscribed
Had to empty the cache table manually, and delete uuid module, too.

Was unaware of the lack of upgrade path, not that this would really give me any other option, but the new version was insisted on by update module because alpha2 is listed as 'recommended release'. I would reconsider that!

TribalMan’s picture

http://drupal.org/node/1256888#comment-4897834

Run these queries, delete the UUID module and manually truncate the cache table.

Honza Pobořil’s picture

TribalMan #16: And enable UUID module again (because I need it as dependency of the Deploy) and I am in trouble again.

We need solution.

rory_o’s picture

Priority: Normal » Major

What timing because I just started using Deploy and the latest version won't work with UUID a1 as some functions aren't available that Deploy needs. We seriously need a solution. I'm resetting to 'major' because completely breaking sites and sitting on it for a couple months is pretty major if not critical. Other modules depended on uuid like Node Export from @danielb and people can inadvertently end up with broken sites.

doublejosh’s picture

#12 Saved me!

mareshal’s picture

what i did and solved the problem is actually taking a look at the fields that are causing the error and then adding them in the db, i.e. base.created is unavailable, i added it in the table file_managed as a date field. Promoted, sticky , published .. can be added as boolean with null as default. it solved the problem till now. there seems to be missing fields in the tables .
Walid.

dixon_’s picture

I want to add a big disclaimer here; neither Deploy or UUID are ready for serious production use yet.

kevinquillen’s picture

This does not work for me.

Does anyone know how to fix it? I did #12, deleted UUID, and I still cannot get into my site. One drush update blew my site all to hell.

@(*#$& heres what I had to do:

Revert back to the old UUID (from drush backup or git revert)
Restore a working database
Run drush rr (registry rebuild) and drush cc all
Go to Modules
Disable UUID, then Uninstall UUID
Proceed to upgrade other modules with drush

This got me back on my feet.

dixon_’s picture

Status: Postponed » Fixed

This should now be fixed in 7.x-1.x-dev and the alpha3 release that I'm rolling right now. Read the upcoming release announcement for more info.

dixon_’s picture

Version: 7.x-1.0-alpha2 » 7.x-1.x-dev
danielb’s picture

awesome

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

gboggs’s picture

Has anyone gotten uuid to upgrade with either the dev release or alpha 3? This is important if you're going from Drupal 6 to Drupal 7 and want to maintain references.

This is all I get when I run /update.php

ResponseText: Fatal error: Call to undefined function uuid_schema() in /var/www/sites/all/modules/contrib/uuid/uuid.install on line 123

A quick grep of uuid.install turns up no definition for uuid_schema(). The function exists in the Drupal6 version of the module, but I imagine their are significant differences between the two functions. Google turned up very little to nothing so far.

Ideas?

DLBaker’s picture

Status: Closed (fixed) » Needs work

In regards to #27,

I have the same issue. We are working on upgrading from D6 to D7 and we must maintain the Unique ID's. Starting from scratch is not an option.

Can anyone shed some light on this upgrade path?

- Dan.

rcross’s picture

Status: Needs work » Closed (fixed)

perhaps try doing a D2D migration rather than an upgrade.

I think we should keep this issue closed and open an new one since you're talking about an upgrade path from D6 to D7 which is different to the original post which affects updates from D7 alpha1/2. Please keep in mind that neither d6 or d7 versions are listed as ready for production use.

glenshewchuck’s picture

In addition to supakitk's fix, note that if you were running memcache like I was you may also have to flush memcache (I killed the processes to respawn it).

drupalfox’s picture

Issue summary: View changes

Hi

We are getting similar issue with deployment. Is there any solution found on this issue.

milos.kroulik’s picture

Status: Closed (fixed) » Active

I also experienced this problem after uninstalling 7.x-1.0-alpha6 version. Given other reports made after marking this as solved, I think, we should set this back to active. #12 is a hotfix, not a patch to be worked on.

skwashd’s picture

Status: Active » Closed (fixed)

@milos.kroulik as per @rcross' comment from 2 years ago the original issue is fixed. If you are still experiencing problem, please open a new (and detailed) issue. Closing.