Answers.Body: <p>Note that when reloading the database,  it is a lot safer and cleaner to load the database dump into a newly created database. If you reload into an existing database, newly created tables will still exist, which fools the upgrade scripts</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-13T22:41:40.503Z
Answers.LastActivityDate: 2015-04-13T22:41:40.503Z
Answers.UserDisplayName: Donald Lobo
Answers.Body: <p>Thanks for adding a bit of detail about the error in your comment. FYI you can edit your question which is even more helpful. And in this case I'm hoping you can provide the exact error on the upgrade when you try to do it from a restored database and restored file system.</p>
  
  <p>When rolling back you should likely carry out steps 9-13 and 16 at <a href="http://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location" rel="nofollow">http://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location</a>. Can you provide more details of the errors you are experiencing after doing that?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-13T21:43:50.463Z
Answers.LastActivityDate: 2015-04-13T21:43:50.463Z
Answers.UserDisplayName: Joe Murray
Body: <p>When trying to upgrade to civi 4.6, the process does a partial upgrade and then errors out.  Recovering previous version reveals SMS is no longer working. What should I do?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T20:41:23.440Z
Comments.Text: This is the error -  Database check failed - the database looks to have been partially upgraded. You may want to reload the database with the backup and try the upgrade process again.
Comments.UserDisplayName: user21507
Tags: <upgrade><sms>
Title: What to do when upgrade to 4.6 failed, but rolling back breaks SMS?
ThreadText: # What to do when upgrade to 4.6 failed, but rolling back breaks SMS?
  
  (Asked by: username_0 on 2015-04-13)
  
  When trying to upgrade to civi 4.6, the process does a partial upgrade and then errors out. Recovering previous version reveals SMS is no longer working. What should I do?
  
  **Tags:** upgrade, sms
  
  > **Comments:**
  > **username_0**: This is the error -  Database check failed - the database looks to have been partially upgraded. You may want to reload the database with the backup and try the upgrade process again.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-04-13. Score: 3
  
  Note that when reloading the database, it is a lot safer and cleaner to load the database dump into a newly created database. If you reload into an existing database, newly created tables will still exist, which fools the upgrade scripts
  
  
  ---
  
  ### Answer by username_2 on 2015-04-13. Score: 2
  
  Thanks for adding a bit of detail about the error in your comment. FYI you can edit your question which is even more helpful. And in this case I'm hoping you can provide the exact error on the upgrade when you try to do it from a restored database and restored file system.
  
  When rolling back you should likely carry out steps 9-13 and 16 at <http://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location>. Can you provide more details of the errors you are experiencing after doing that?
  
  
  ---
  
  