Your database has already been upgraded to CiviCRM 4.5.5

[magnolia61]

Hi folks,
I just tried to upgrade our 4.5.5 / drupal 734 site to the new civicrm 4.5.6.
After wgetting and tarring I tried to upgrade but got the following error:

Sorry but we are not able to provide this at the moment.
Your database has already been upgraded to CiviCRM 4.5.5

What can I do to complete the upgrade process? Is this a bug?

[Coleman Watts]

Are you sure you unpacked the new code in the right place?

[flo81]

Have you find out what was happening ? I have the same problem trying tu upgrade from 4.5.4 to 4.5.8. I can still access Civi, my datas are still in place but in the footer I still have "CiviCRM 4.5.4", and /civicrm/upgrade?reset=1 displays "Your database has already been upgraded to CiviCRM 4.5.4".

I'm using the Drupal module (Drupal 7.34).

[magnolia61]

I have the exact same problem upgrading from 4.5.6 to 4.5.7 or 4.5.8
"Your database has already been upgraded to CiviCRM 4.5.6"

I wget the package, untar it in /domains/onvergetelijk.nl/public_html/crm/sites/all/modules
I even renamed my old folder to civicrm-bak to be sure I was unpacking in the proper folder.

[joanne]

Are you following the upgrade instructions at http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+4.5+-+Drupal+7 ?  In particular:

7. Backup and then delete all previous version code files

CiviCRM will not run properly if files from previous version are present after the upgrade. Make sure you have a good backup of your complete previous version installation and then delete /sites/all/modules/civicrm.
   

Be sure that your backup copy of the previous version codebase is NOT located below the <drupal home>/modules or <drupal home>/sites/all/modules directory. For example, placing your codebase backup in <drupal home>/modules/civicrm.bak... will cause errors (Drupal executes any *.module files that are found in the modules or sites/all/modules directory tree).

[Hershel]

I even renamed my old folder to civicrm-bak to be sure I was unpacking in the proper folder.

You can't do that--you must either remove it or move that "old folder" to a different location. If it's still in sites/all/modules, then Drupal will detect it.

[wimvanaelst]

I meant:
I even renamed my old folder to civicrm-bak * and then deleted it before running the upgrade * to be sure I was unpacking in the proper folder.

Anyway, today I installed the 4.6.2 update, and it ran flawless.
I am not sure why it did not work the previous update, but I'm glad the glitch is not there anymore.