Answers.Body: <p>As Lindsey D pointed out in the comment, the answer was to restore the database backup from the automatic backup located in <code>/craft/storage/backups</code> that is generated when the update was initiated.</p>
  
  <p>When this backup is put into place it will re-run the database migration when you visit the Admin area.</p>
  
  <p>So my full solution was 2 steps: </p>
  
  <ol>
  <li>Replace /craft/app with a fresh copy</li>
  <li>Restore the automatically backed up database in <code>/craft/storage/backups</code></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-04T03:31:02.417Z
Answers.LastActivityDate: 2016-02-04T03:31:02.417Z
Answers.UserDisplayName: Jason D
Body: <p>A client upgraded their site to 2.5, and I believe the update didn't finish.</p>
  
  <p>At first there was a 500 error. I tried rolling the app back (code only) and it  gave an error that the database version didn't support rolling back. Replacing the <code>craft/app</code> directory with a fresh version of 2.5 fixed the 500 error.</p>
  
  <p>The site and some of the admin area work, but in the control panel I cannot access Assets or Entries, I get this error:</p>
  
  <p><code>CDbCommand failed to execute the SQL statement: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mysite.craft_elementindexsettings' doesn't exist</code></p>
  
  <p>So it seems like something with the migration failed. Except must have not been fully failed, because of the error I got about the database version.</p>
  
  <p>The catch is that the client didn't do a database backup before initiating the update, so there isn't a good rollback point. </p>
  
  <p>Could I manually add this table? Any other potentially fixes for this? Is there a way to tell Craft to re-run the migration to 2.5?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-02-04T02:55:51.040Z
Comments.Text: Unless it's disabled, Craft will [automatically perform a DB backup](https://craftcms.com/docs/config-settings#backupDbOnUpdate) before running an update. Were automatic backups disabled?
Comments.UserDisplayName: Lindsey D
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-02-04T03:27:34.083Z
Comments.Text: Oh, thank you. I didn't realize this. Importing that backed up database initiated the migration and the problem is fixed. For anyone finding this unfamiliar with where the automatic backup is, it's /craft/storage/backups
Comments.UserDisplayName: Jason D
Tags: <auto-updates><updating>
Title: After upgrading to 2.5: Table 'alpineductless-craft.craft_elementindexsettings' doesn't exist
ThreadText: # After upgrading to 2.5: Table 'alpineductless-craft.craft_elementindexsettings' doesn't exist
  
  (Asked by: username_0 on 2016-02-04)
  
  A client upgraded their site to 2.5, and I believe the update didn't finish.
  
  At first there was a 500 error. I tried rolling the app back (code only) and it gave an error that the database version didn't support rolling back. Replacing the `craft/app` directory with a fresh version of 2.5 fixed the 500 error.
  
  The site and some of the admin area work, but in the control panel I cannot access Assets or Entries, I get this error:
  
  `CDbCommand failed to execute the SQL statement: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mysite.craft_elementindexsettings' doesn't exist`
  
  So it seems like something with the migration failed. Except must have not been fully failed, because of the error I got about the database version.
  
  The catch is that the client didn't do a database backup before initiating the update, so there isn't a good rollback point.
  
  Could I manually add this table? Any other potentially fixes for this? Is there a way to tell Craft to re-run the migration to 2.5?
  
  **Tags:** auto-updates, updating
  
  > **Comments:**
  > **username_1**: Unless it's disabled, Craft will [automatically perform a DB backup](https://craftcms.com/docs/config-settings#backupDbOnUpdate) before running an update. Were automatic backups disabled?  
  > **username_0**: Oh, thank you. I didn't realize this. Importing that backed up database initiated the migration and the problem is fixed. For anyone finding this unfamiliar with where the automatic backup is, it's /craft/storage/backups  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-02-04. Score: 3
  
  As username_1 pointed out in the comment, the answer was to restore the database backup from the automatic backup located in `/craft/storage/backups` that is generated when the update was initiated.
  
  When this backup is put into place it will re-run the database migration when you visit the Admin area.
  
  So my full solution was 2 steps:
  
  1. Replace /craft/app with a fresh copy
  2. Restore the automatically backed up database in `/craft/storage/backups`
  
  
  ---
  
  