Forums / Upgrading to 1.5.x / After DB upgrade, still getting "database upgrade required" message

After DB upgrade, still getting "database upgrade required" message

Started by wygk on 6 Oct 2012, 7:03 PM · Views: 1,998

Results 1 to 6 of 6
6 Oct 2012, 7:03 PM
#1
wygk avatar

wygk

New Zenner

Join Date:
Sep 2009
Posts:
14
Plugin Contributions:
0

After DB upgrade, still getting "database upgrade required" message

As per the instructions, I made a copy of my 1.3.9 database to preserve my date, then ran zc_install.

I ran the "Upgrade DB from 1.3.9 to 1.5.0" and " Upgrade DB from 1.5.0 to 1.5.1" and got a few messages about things that could not be dropped (because they didn't exist) or added (because they already exist). Based on the instructions, I assumed these errors would not cause problems.

I got to the page that said:

Congratulations!
You have successfully installed Zen Cart® on your system!

However, when I went to the admin page, I got the following error:

"database upgrade required. please run the 1.3.9-to-1.5.0 upgrade via zc_install"

I tried deleting and recreating the database. I also tried running the two database upgrade steps separately, as opposed to checking both at the same time. The results are always the same.

How do I go about tracking down the problem?

6 Oct 2012, 7:08 PM
#2
kobra avatar

kobra

Black Belt

Join Date:
Aug 2005
Location:
Arizona
Posts:
31,500
Plugin Contributions:
4

Re: After DB upgrade, still getting "database upgrade required" message

I got to the page that said:

Congratulations!
You have successfully installed Zen Cart® on your system!
You should not be seeing this when running zc_install and selecting database upgrade

Zen-Venom Get Bitten

6 Oct 2012, 7:18 PM
#3
wygk avatar

wygk

New Zenner

Join Date:
Sep 2009
Posts:
14
Plugin Contributions:
0

Re: After DB upgrade, still getting "database upgrade required" message

MORE INFO:

Here are the messages I get after "Upgrade DB from 1.3.9 to 1.5.0"

SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.

And here are the contents of the zc_upgrade_exceptions table:

| 1 | sql/mysql_upgrade_zencart_139_to_150.sql | Cannot drop index page_accessed on table admin_activity_log because it does not exist. | 2012-10-06 14:14:05 | ALTER TABLE admin_activity_log DROP INDEX page_accessed; |
| 2 | sql/mysql_upgrade_zencart_139_to_150.sql | Cannot drop index access_date on table admin_activity_log because it does not exist. | 2012-10-06 14:14:05 | ALTER TABLE admin_activity_log DROP INDEX access_date; |
| 3 | sql/mysql_upgrade_zencart_139_to_150.sql | Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists. | 2012-10-06 14:14:05 | ALTER TABLE admin_activity_log ADD INDEX idx_page_accessed_zen (page_accessed); |
| 4 | sql/mysql_upgrade_zencart_139_to_150.sql | Cannot add index idx_access_date_zen to table admin_activity_log because it already exists. | 2012-10-06 14:14:05 | ALTER TABLE admin_activity_log ADD INDEX idx_access_date_zen (access_date); |

There are no additional errors after I run "Upgrade DB from 1.5.0 to 1.5.1" ... the "Zen Cart® Setup - Finished" page is displayed. But at that point, if I try to go to the admin page, I get the "database upgrade required. please run the 1.3.9-to-1.5.0 upgrade via zc_install" message.

6 Oct 2012, 7:26 PM
#4
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,511
Plugin Contributions:
176

Re: After DB upgrade, still getting "database upgrade required" message

wygk:

MORE INFO:

Here are the messages I get after "Upgrade DB from 1.3.9 to 1.5.0"

SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.
Those are normal. Can be ignored.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

6 Oct 2012, 7:27 PM
#5
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,511
Plugin Contributions:
176

Re: After DB upgrade, still getting "database upgrade required" message

Chances are your /renamed_admin_folder/includes/configure.php file contains DB_XXXXX settings that are different from your /includes/configure.php DB_XXXXX settings.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

6 Oct 2012, 7:53 PM
#6
wygk avatar

wygk

New Zenner

Join Date:
Sep 2009
Posts:
14
Plugin Contributions:
0

Re: After DB upgrade, still getting "database upgrade required" message

YES!

That was exactly the problem. Pretty obvious, in retrospect (as is often the case). I was SURE I had replaced the admin/includes/configure.php file

Thanks so much for catching this!