Answers.Body: <p>You can see exactly what queries are being run by this incremental upgrade by opening up the <a href="https://github.com/civicrm/civicrm-core/blob/4.6/CRM/Upgrade/Incremental/sql/4.6.4.mysql.tpl" rel="nofollow">CRM/Upgrade/Incremental/sql/4.6.4.mysql.tpl</a>. In this case it's basically nothing. There is one query in there, which you could copy and paste into e.g. PHPMyAdmin and run it from there (although it honestly doesn't look very important).</p>
  
  <p>Normally I would worry about a hung upgrade and recommend you restore from backups and try again. But in this case I think you lucked out.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-20T16:50:54.810Z
Answers.Text: Thanks, I have checked the sql-statement and it was performed in the upgrade.
  The grouptype was changed (the grouptype is now as it should be according the sql-statement).
Answers.UserDisplayName: HanV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-18T20:17:56.867Z
Answers.LastActivityDate: 2015-06-18T20:17:56.867Z
Answers.UserDisplayName: Coleman
Body: <p>I tried to upgrade version 4.6.3 (Drupal 7.37, dutch) to version 4.6.4.
  After upgrading the database, <code>[Executed: Upgrade DB to 4.6.4]</code>
   the process seemed to stop on 2/3 of the bar. 
  After 10 minutes I tried to use CiviCRM and it worked showing version 4.6.4.</p>
  
  <p>There are no errors in the logfile server or on screen, in civicrm.log the normal logging <code>[Executed: Upgrade DB to 4.6.4]</code> and <code>[upgrade:4.6.4.upgrade-&gt;4.6.4]</code></p>
  
  <p>Maybe the problem was that I first tried the upgrade without being signed in on Drupal. After the error I started the upgrade again and it did not completed, but CiviCRM works.</p>
  
  <p>Will this cause problems going forward or am I okay?</p>
  
Tags: <upgrade>
Title: Upgrade from 4.6.3 to 4.6.4 not completed
ThreadText: # Upgrade from 4.6.3 to 4.6.4 not completed
  
  (Asked by: username_0 on 2015-06-18)
  
  I tried to upgrade version 4.6.3 (Drupal 7.37, dutch) to version 4.6.4.
  After upgrading the database, `[Executed: Upgrade DB to 4.6.4]`
  the process seemed to stop on 2/3 of the bar.
  After 10 minutes I tried to use CiviCRM and it worked showing version 4.6.4.
  
  There are no errors in the logfile server or on screen, in civicrm.log the normal logging `[Executed: Upgrade DB to 4.6.4]` and `[upgrade:4.6.4.upgrade->4.6.4]`
  
  Maybe the problem was that I first tried the upgrade without being signed in on Drupal. After the error I started the upgrade again and it did not completed, but CiviCRM works.
  
  Will this cause problems going forward or am I okay?
  
  **Tags:** upgrade
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-06-18. Score: 1
  
  You can see exactly what queries are being run by this incremental upgrade by opening up the [CRM/Upgrade/Incremental/sql/4.6.4.mysql.tpl](https://github.com/civicrm/civicrm-core/blob/4.6/CRM/Upgrade/Incremental/sql/4.6.4.mysql.tpl). In this case it's basically nothing. There is one query in there, which you could copy and paste into e.g. PHPMyAdmin and run it from there (although it honestly doesn't look very important).
  
  Normally I would worry about a hung upgrade and recommend you restore from backups and try again. But in this case I think you lucked out.
  
  > **Comments:**
  > **username_0**: Thanks, I have checked the sql-statement and it was performed in the upgrade. The grouptype was changed (the grouptype is now as it should be according the sql-statement).  
  
  ---
  
  