Upgrade from 1.0-rc5 fails: Table 'pathauto_state' doesn't exist

Sorry to have to reopen this. This is still happening for my upgrade from rc5 to 7.x-1.1+23-dev

WD php: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'example.pathauto_state' doesn't exist: SELECT entity_id, pathauto FROM {pathauto_state} WHERE entity_type = :entity_type AND entity_id IN (:entity_ids_0); Array
(
    [:entity_type] => user
    [:entity_ids_0] => 0
)
 in pathauto_entity_state_load_multiple() (line 436 of /data/www/panopoly/profiles/panopoly/modules/contrib/pathauto/pathauto.module).

It's a straight panopoly installation without any other distributions, profiles and the only patched panopoly module is entityreference (to fix a field_collection issue). I do have a lot of additional contrib in sites/all/modules/contrib that are enabled on my site but this pathauto_state problem is the only error I get when running updates.

I don't mind trying something drastic if you have any ideas. I have lots of backups.

OK, I got this working but it did require the following workaround:

1. Download a fresh copy of pathauto (1.2) into sites/all/modules/contrib/pathauto
2. Run a registry rebuild to update module path to use the sites/all/modules/contrib/ version of pathauto
3. Run updates. All of the other module updates (around 20) run successfully and the pathauto update is not triggered.
4. Delete pathauto from sites/all/modules/contrib/pathauto
5. Run another registry rebuild
6. Run updates. This time, the only update left was pathauto, which runs successfully

I'll let you decide whether the issue should be closed again or if you'd like to further review the issue based on this result.

You are running into #2230419: Distribution updates run in an unpredictable order.

I just wanted to post my experience with this issue. We are updating from Panopoly rc4 to 1.2, and encountered this problem (it appears as though rc5 is when the table name changed from 'pathauto' to 'pathauto_state'.) The workaround used by @mducharme in #8 didn't work for me, as the table still wasn't created. What I wound up doing was hacking the code a bit to add a conditional statement to the 3 functions that access the database table. If the 'pathauto_state' table existed, it would use it, otherwise, it would use 'pathauto.' This was only necessary to keep the site alive so I could run drush updb. Once the database updates ran, the table was created, and the conditionals could be removed.

I could post a patch if anyone needs it, but this is really just a simple hack to allow the database updates to run and probably won't affect many users.

#8 worked for me, thanks for posting, mducharme!

ugh... i just got this message while trying to finish an update. how can i tell the order of the updates? i have a quite a number of modules outside of the Panopoly bundle :P

*sigh* still have this problem with 1.4.
here's the print out to the update order

Block 7009 Increase {block}.title length to 255 characters.
Panopoly_core 7102 Disable Panopoly layouts and enable Radix ones.
Panopoly_theme 7002 Enable radix_layouts and clear layouttheme caches.
Panopoly_theme 7003 Switch all Panels in the database to use Radix layouts.

Initialized Drupal site default at sites/default

Executing panopoly_theme_update_7002

Performed update: panopoly_theme_update_7002

Executing panopoly_theme_update_7003

Performed update: panopoly_theme_update_7003

Executing panopoly_core_update_7102

Performed update: panopoly_core_update_7102

Executing block_update_7009

Performed update: block_update_7009

Command dispatch complete

will try out #8 and report back
*siiiiiiiiiiiiiiiihg*

tried a few variations of #8 and nothing works. suggestions?

not solved for me wit 1.4

Running /update.php fixed this error for me.