Errors on 1.5.1 to 1.5.7c

standard load of new 1.5.7c, remove new database, bring in old database, zc_install for upgrade, bombs out every time saying I have 1.5.2 and must perform 1.5.3 first.

I have used all the arrows in my quiver including the date fix and cannot get past this point. database says version is 1.5.3.

What am I missing? Probably something simple as pain meds are wearing off.

[Attachment no longer available]

One of the SQL updates didn't work and a subsequent check for it failed.
This is almost always because you have added a date to a table and the date format hasn't been fixed.
There will be upgrade logs in your logs folder that you can review. See also:

https://docs.zen-cart.com/user/upgrading/date_standardization/

https://docs.zen-cart.com/user/upgrading/could_not_upgrade/

dbltoe:

I have used all the arrows in my quiver including the date fix and cannot get past this point. database says version is 1.5.3.

And, there are no upgrade logs.:frusty:

dbltoe:

And, there are no upgrade logs.:frusty:

Has the admin been accessed after the last attempt to upgrade the database? This code section of the admin deleted some of the logs associated with install: https://github.com/zencart/zencart/blob/70ee017b767cef35affdf980f47b9ec1dee2e8a0/admin/includes/init_includes/init_errors.php#L202-L211

Specifically at: https://github.com/zencart/zencart/blob/70ee017b767cef35affdf980f47b9ec1dee2e8a0/admin/includes/init_includes/init_errors.php#L206

// log cleanup for zc_install "info logs". This still leaves behind any zcInstallDEBUG or zcInstallException log files
  if ($za_dir = @dir(DIR_FS_LOGS)) {
    while ($zv_file = $za_dir->read()) {
      if (preg_match('/^zcInstallLog.*\.log$/', $zv_file)) {
        unlink(DIR_FS_LOGS . '/' . $zv_file);
      }
    }
    $za_dir->close();
    unset($za_dir);
  }

They are deleted relatively quickly after performing the upgrade, once the admin is accessed after performing the upgrade attempt.

I suspect following the second link above from swguy will assist in addressing the issue.

The second link points you to the file zc_install/includes/systemChecks.yml.
For 153, that file checks two things: customers.customers_password (makes sure it is varchar(255)) and admin.admin_pass (same check).
Have you modified those fields?

I will check. I've inherited an upgrade that has been "adapted" by many in the past.

First time to run into a problem like this.:(

customers.customers_password was 40:ohmy:

Got it going now.

THANX