Database Version Mismatch.
Posted by - NA -, Last modified by Wayne Smith on 20 August 2014 01:02 PM

==================
Database Version Mismatch.
==================


Symptom
---------
Error: Database Version Mismatch - Expected version 4.13 found 4.24


Cause
------
This error occurs when the MIVA Merchant databases and scripts are two different versions. The above example can occur when a customer has upgraded from 4.13 to 4.24, but has not updated their links to go to the new compiled .mvc pages.



Solution
----------
Make sure that the data and scripts are both the same version.

The error can also be reversed.
Example: Database Version Mismatch - Expected version 4.24 found 4.13

When this happens, it means that the scripts were upgraded, but the databases were not. In this case, if the customer has already attempted an upgrade, the best solution would be to restore the backup and start the upgrade again to ensure that all databases are properly upgraded.

A rewrite can be put in place as well to handle the .mv to .mvc change.

#REWRITE .mv to .mvc when .mvc file exists
RewriteEngine on
RewriteBase /
RewriteRule ^(.*).mv$ $1 [C,E=WasMV:yes]
RewriteCond %{REQUEST_FILENAME}.mvc -f
RewriteRule ^(.*)$ $1.mvc [S=1]
RewriteCond %{ENV:WasMV} ^yes$
RewriteRule ^(.*)$ $1.mv

See "How to keep Miva Merchant stores working after upgrading from uncompiled to compiled?"
https://support.mivamerchant.com/supportsuite/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=547

(147 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako support.miva.com/supportsuite/index.php?