[Not a ZC Bug] Duplicate use of order numbers v1.3.9h

Hello
About three weeks ago I did a clean install of v1.3.9h the data base was from my 1.38. The site has a few addons nothing new this time from the 1.38 version.

The order generation is not working properly in that it is using the same order number more then once. It sends both orders using the same number to our email notification but it only shows one order in our admin page. There are still some orders that are processing correctly so it is intermittent and we first notice this problem a little over a week after starting to use the new version. Drop me a note if you have any ideas of what might be going on. The site is at https://www.makupartist.com
Thanks for your help
Cheers
T

I'm not sure I understand. Zen Cart cannot use the same order number more than once, because the order number is based on a unique-only field in the database, which prevents it from ever re-using an existing order number.

Have you installed or written some addons that have changed how your store handles order numbers?

Hi
No I just did a fresh install, everything went well. I just had it send through an order 443 that was already used by another customer, at the same time order 444 was already there but it skipped back to order 443. The original customer who used 443 does show in my admin but the second one is not recorded but I do have now have two email notifications for 443. Should I try a repair on the data base or something else?
Thanks
T

Hi
I repaired the database tables and optimized them but when I run a check in phpMyAdmin I get this message
latexinn_zen139.configuration check warning Found row where the auto_increment column has the ...
latexinn_zen139.configuration check status OK
latexinn_zen139.configuration_group check warning Found row where the auto_increment column has the ...
latexinn_zen139.configuration_group check status OK

All other tables came up Ok
Any suggestions?

Seems pretty clear that you've got a database integrity problem.

You'll need to verify that all the structures match the original official structures, and repair any damaged data.

Hi
The error message is in the configuration table and I compared the old one with the new one and the only difference I could find was on Cardinality, the original looks like this: PRIMARY BTREE Yes No configuration_id 882 A
unq_config_key_zen BTREE Yes No configuration_key 882 A
idx_key_value_zen BTREE No No configuration_key 882 A
configuration_value (10) 882
and the new one in version 139 looks like this: PRIMARY BTREE Yes No configuration_id 871 A
unq_config_key_zen BTREE Yes No configuration_key 871 A
idx_key_value_zen BTREE No No configuration_key 871 A
configuration_value (10) 871

Is it standard for it to be 882?
Thanks
T

Hi
Looks like I fixed it by turning off and on auto increment. I just did a test purchases and it advanced the count
T