Fields collection conflict

If you have upgraded to latest version of field collection then you will have this problem.
field collection module has implemented revision support in the latest version
i think accordingly all the contribs which require field collection as dependency should revise their modules accordingly

I upgraded field_collection from beta-4 to beta-5 using the standard drupal upgrade process. The upgrade succeeded, there are no pending database upgrades. However, upon attempting to access any content that uses field_collection, I also receive the fatal PDO error about the base table field_collection_item_revision not existing. A quick look in the database confirms...no table.

Here's what this seems to boil down to: The scheme for field_collection needs to be updated to support revisions when upgrading to beta-5. If your site actually uses field_collection, you can't upgrade the schema because its a required component of drupal. So the codebase updates, without the database updates, and your site breaks. Of course, you can get the site working again by manually adding the proper components to the db:

- Add the field_collection_item_revision table (you can import an empty one via the attached .sql file)
- Add two fields to the field_collection_item table: revision_id, archived; both should be INT(11), NOT NULL, and archived has a default of 0

This gets your site to *run* again. However, throws countless errors because even though the fatal errors of missing tables are gone, the revisions for your current content dont exist! However, this is obviously NOT the right way to do things, and I would welcome anyone who knows of a patch to fix it.

You can clear up the addition errors by performing the following SQL:

UPDATE field_collection_item SET revision_id = item_id

Then in the field_collection_item_revision table, create a simple entry for each item_id in the field_collection_item table where item_id = both revision_id and item_id

The SQL that implements the above idea

INSERT INTO field_collection_item_revision (item_id, revision_id)
SELECT item_id, item_id FROM field_collection_item

You will also need to update any already created field collections with the following SQL statements

ALTER TABLE  `field_data_{FIELD_NAME}` ADD  `{FIELD_NAME}_revision_id` INT( 11 ) NOT NULL AFTER  `{FIELD_NAME}_value`;

UPDATE `field_data_{FIELD_NAME}` SET `{FIELD_NAME}_revision_id` = `{FIELD_NAME}_value`;

Next hurdle appears to be that field collection isn't setting the {FIELD_NAME}_revision_id column correctly on new collection inserts.

I am also facing some problems with this

I taking same error. But simply need execute updates:

field_collection module : 
  7001 -   Add revision support. 
  7002 -   Remove orphaned field collection item entities. 

So for me, this task fixed

To fix this, I opened the database, found the {system} table, searched for the row with name = field_collection, and changed the schema version from -1 to 7000. I then ran the database update script.

Thanks Jaypan... your fix helped me out.