ShopSite 10 Error Message: "column ss_UUID is not uniqu

[DDreslough]

We just upgraded to ShopSite 10 (on FreeBSD), and had a customer get this error repeatedly today.

"Digital Download SQL INSERT failed: Query failed: column ss_UUID is not unique(19)"

Also, at our credit card payment gateway, this transaction showed up as an Result Code 105: N transaction, which according to PayPal_ToddS at http://www.paypaldeveloper.com/pdn/boar ... 4408#M4068 means "A transaction type of "N" means the transaction is a duplicate. ie the same transaction was sent in twice. The "N" transaction is NOT a valid transaction."

Only one customer got it, but I've never seen anything like it and it makes me a bit nervous. These things have a way of repeating and we lose sales. Any ideas? We sell a downloadable PC game.

We haven't had any other customers get this error yet, but I would like to know a workaround if it happens again.

Thank you!

-Dee Dreslough
dee@sportsmogul.com
www.sportsmogul.com

[Jim]

I haven't heard of this problem but it sounds like you need to work with your host and have them contact ShopSite support for assistance.

[DDreslough]

I had a user today enter an order. He got his CSC wrong, so he typed his info in again -- It created a transaction at the Payflow Pro end that referenced his original failed transaction, and looked like it was approved, but it was an "N" transaction...but he never got his product...and I can't refund anything which makes me think he wasn't really charged either.

Frustrated, he put in yet another card and got the same result again...
He's still without his product -- we're still without our money from what I can see, and we're all very confused.

What is shopsite doing when he hit 'back' and entered his card info again? Here's what we're seeing (the names have been changed to protect the innocent):

ID----------Type-Card---RESPONSE MESSAGE
Vblah1-----Sale--Visa----Declined
Vblah2-----N-----N/A-----Approved
Vblah3-----N-----N/A-----Approved

Each of the "N" type transactions (defined above) reference the original failed transaction and have a money amount ($19) associated with each, but don't check for CSC, AVS Street Match, AVS Zip match or anything. They just dump the whole thing to an "N" transaction instead of using the new info to try to run the card.

And, I can't credit him back anything, so I'm pretty sure he didn't get charged.

Do I need to inform my users that if their transaction fails they should completely cancel the order and start from scratch or something?

I'm on ShopSite 10, and I"m worried this is a bit of a bug. I think users should be able to go back and re-enter their data if they accidentally mis-enter their card data once. Making them completely re-order is going to cost us some sales.

Am I not understanding something here, or is there a bug?

-Dee Dreslough
dee@sportsmogul.com
www.sportsmogul.com

[ShopSite David]

This issue was recently addressed in a patch. Have your host apply the patches and then your ShopSite version should display as v10 r6.1. See:
http://support.shopsite.com/KBase/questions/2514/