.BAD Orders?

[Rick Hendrickson]

We are running Shopsite Pro 8.1 on a Windows box. We recently had a skip in sequence in our order numbers. When I looked in the /data/.../ip directory, I noticed that the order files were named with a .BAD extension. For example, one of the orders we were missing was order #17641. In the ip/ directory, there is a file called iorder.17641.bad instead of iorder.17641.done. We have four such orders/files recently. What triggers a file to be labeled "bad"?

[Jim]

The ShopSite username is case sensitive but Windows doesn't care about case. So if you logged in as "User" and the ShopSite login name is "user" Windows would allow you to login and you could see things in the backoffice but if you try to pull in orders it would try and match your login name with the store login name and if they don't match the orders would be marked as bad. A fix for this was made at some point but since you are running an old version it may not be in the version you are using.

You can rename the .bad orders to .new and try to import them again.

[loren_d_c]

Logging in with the wrong upper/lower case in the username on a Windows ShopSite should not cause this problem if you have ShopSite v6.3 or newer. So a more likely issue in v8.1 (assuming you haven't changed your ShopSite license file recently) is a problem writing to the main ShopSite database when accessing the Orders menu. Check the status of the database from the Utilities -> Database menu, and if it reports any errors try the Compact function to see if it resolves them. If it does, or if the database status is OK in the first place, then try renaming the iorder.[ordernum].bad files with a .new extension and then go to the Orders menu again and see if those orders come in this time.

-Loren