I know this has been discussed before, scattered amongst many topics, but I don't know if I ever got a concrete solution for it.
Problem: When a customer with a foreign character in their name/address tries to place an order, it gets declined by FirstData/Linkpoint processor. The exact error is: Response Code: SGS-020003: Invalid XML
For example, if it has a character like these (ñ, í, é, etc), then the transaction declines.
Suspected Reasons Why: I think this has SOMETHING to do with mixed up COLLATION in the database. Either an entire TABLE collation is wrong, or perhaps individual fields within a table have incorrect collection.
WHAT I NEED TO KNOW:
- Can someone tell me straightforwardly, in order to avoid this Invalid XML message with customers who have foreign characters in their addresses, WHAT TABLES would effect this, and WHAT COLLATION should they be?
For example, perhaps you could say something like "The only tables which would effect this kind of error would be TABLE-X and TABLE-Y, and those table should be COLLATION-Z to avoid that problem."
Here are some of my current settings (on the tables *I THINK* would be the focus of the problem):
- zen_address_book (my collation is utf8_unicode_ci)
- zen_address_format (my collation is utf8_unicode_ci)
- zen_customers (my collation is latin1_swedish_ci)
- zen_linkpoint_api (my collation is latin1_swedish_ci)
- zen_orders (my collation is utf8_unicode_ci)
To further confuse things, some of my tables have MIXED collation inside of them. For example, my zen_customers table has a global collation of latin1_swedish_ci. And yet, if I look at the structure of each field INSIDE of that table, the fields themselves have the utf8_unicode_ci collation:
Attachment 13977
Attachment 13978
As you can see, my GUESS is that this XML error happens because of some database misconfiguration on my part, and I would just need to know what collation to change (which field, or which table, etc).
Bookmarks