Re: UPS XML: Support Thread
Quote:
Originally Posted by
swguy
Upgrade won't help (although obviously you will want to do it at some point). The issue you are hitting is that there is something in the message you are sending which makes the XML invalid. Look for things like ampersands or quotes embedded in product names or perhaps in the customer's address.
what happens if mike d'antonio decides to order? can he not buy anything on the web? or what happens if mike d'antonio wants his product shipped to B&B Italia?
if the malformed XML document is due to one of those issues (and i'm not saying that it is not), then i think we should fix the plugin (or at least help lat9 with it).
are you sure you are using the latest version of the plugin?
Re: UPS XML: Support Thread
Probably helps if I post the UPSXML debug instead of the zencart admin debug, though I don't know why the admin debug would have indications of UPSXML issues and also reference USPS in the same error. Admin error looks like zen-cart.com plugin support check is no longer supported
And to go along with carlwhat comments, I happen to live adjacent to the only town in the usa that has an apostrophe in the name but have learned to use a space instead.
Code:
Date and Time: 2020-02-27 15:24:15
UPS URL: https://onlinetools.ups.com:443/ups.app/xml/Rate
UPS Request: <?xml version="1.0"?>
<AccessRequest xml:lang="en-US">
<AccessLicenseNumber>removedforsecurity</AccessLicenseNumber>
<UserId>Chaingedforsecurity</UserId>
<Password>8XRs2*xzt$KW&xb@</Password>
</AccessRequest>
<?xml version="1.0"?>
<RatingServiceSelectionRequest xml:lang="en-US">
<Request>
<TransactionReference>
<CustomerContext>Rating and Service</CustomerContext>
<XpciVersion>1.0001</XpciVersion>
</TransactionReference>
<RequestAction>Rate</RequestAction>
<RequestOption>shop</RequestOption>
</Request>
<PickupType>
<Code>03</Code>
</PickupType>
<Shipment>
<RateInformation><NegotiatedRatesIndicator /></RateInformation>
<Shipper>
<Address>
<City>Hayden</City>
<StateProvinceCode>LA</StateProvinceCode>
<CountryCode>US</CountryCode>
<PostalCode>83835</PostalCode>
</Address>
<ShipperNumber>6digits</ShipperNumber>
</Shipper>
<ShipTo>
<Address>
<City>Hayden</City>
<StateProvinceCode>ID</StateProvinceCode>
<CountryCode>US</CountryCode>
<PostalCode>83835</PostalCode>
<ResidentialAddressIndicator/>
</Address>
</ShipTo>
<Package>
<PackagingType>
<Code>02</Code>
</PackagingType>
<PackageWeight>
<UnitOfMeasurement>
<Code>LBS</Code>
</UnitOfMeasurement>
<Weight>1</Weight>
</PackageWeight>
<PackageServiceOptions>
<InsuredValue>
<CurrencyCode>USD</CurrencyCode>
<MonetaryValue>142</MonetaryValue>
</InsuredValue>
</PackageServiceOptions>
</Package>
</Shipment>
<CustomerClassification>
<Code>04</Code>
</CustomerClassification>
</RatingServiceSelectionRequest>
UPS RESPONSE: <?xml version="1.0"?>
<RatingServiceSelectionResponse><Response><TransactionReference><CustomerContext>Rating and Service</CustomerContext><XpciVersion>1.0001</XpciVersion></TransactionReference><ResponseStatusCode>0</ResponseStatusCode><ResponseStatusDescription>Failure</ResponseStatusDescription><Error><ErrorSeverity>Hard</ErrorSeverity><ErrorCode>10001</ErrorCode><ErrorDescription>The XML document is not well formed</ErrorDescription></Error></Response></RatingServiceSelectionResponse>
Re: UPS XML: Support Thread
Sorry, should have said UPSXML v1.7.7
Production or Test server: same debug file
Re: UPS XML: Support Thread
problem with your password....
try changing your password and removing the &xb
ahem.... ahem.... cough... cough....
best.
Re: UPS XML: Support Thread
I can see UPS is gonna get me in trouble since there doesn't seem to be any way to differentiate Domestic GROUND from International GROUND as FEDEX allows that differentiation.
This is a troublemaker when it comes to allowing Canadian Customers to choose GROUND . 99% of Canadian Retail Customers do not understand that Customs Clearing is not included in the price and refuse the shipment when it arrives due to UPS Custom Clearing.
Re: UPS XML: Support Thread
Quote:
Originally Posted by
carlwhat
problem with your password....
try changing your password and removing the &xb
ahem.... ahem.... cough... cough....
best.
UPS accepts that password when I login manually. I hate it when I have to manually 'dumb' my password generator.
BUT it is worth a try
TNX
Re: UPS XML: Support Thread
nothing to do with UPS. it's the xml that does not meet validation prior to sending it to UPS. UPS is only telling you that.
as far as password security, removing the ampersand is hardly dumbing down the password... i think (and most experts would now agree) password length is the singlest biggest thing to having a stronger password. old school of utilizing 3 of the 4 character types is not nearly as secure as having a 25 character password.
Re: UPS XML: Support Thread
Quote:
Originally Posted by
carlwhat
nothing to do with UPS. it's the xml that does not meet validation prior to sending it to UPS. UPS is only telling you that.
as far as password security, removing the ampersand is hardly dumbing down the password... i think (and most experts would now agree) password length is the singlest biggest thing to having a stronger password. old school of utilizing 3 of the 4 character types is not nearly as secure as having a 25 character password.
Progress. Thanks. That error has gone away when I changed the UPS password and replaced by another.
Shipping address from checkout screen
Quote:
IMA Customer
9030 N Hess St 171
Hayden, ID 83835
United States
Or tried
Quote:
MA Customer
123 main street
spokane, WA 99202
United States
UPS XML error thinks the address zipcode is in Louisiana???
Quote:
111285: The postal code 83835 is invalid for LA United States.
Re: UPS XML: Support Thread
Quote:
Originally Posted by
RixStix
Progress. Thanks. That error has gone away when I changed the UPS password and replaced by another.
Shipping address from checkout screen
Or tried
UPS XML error thinks the address zipcode is in Louisiana???
rick,
without the logs and specifically the xml that you are sending to UPS and the return string, it is hard to troubleshoot the problem.
UPS utilizes the USPS database of all US addresses. so if they are returning an error on address validation, then it is possible the USPS database has an error in its database.
with regards to the shipping addresses you have tried, the first address is a valid address, and it should come back fine. now because it did not, there is probably a problem with what you are sending them, which is why the logs are useful. that address validates as such:
Del address.. 9030 N HESS ST 171
Last line.... HAYDEN ID 83835-9827
Delivery point / check digit..... 30 4 Carrier route id.................. R008
eLOT sequence no / A/D code.... County.... KOOTENAI ID
FIPS state / county no......... 16 055 Congressional district........... ID 01
Early Warning System flag........... LACS indicator.......................
DPV confirmation indicator.......... S DPV CMRA indicator................... Y
DPV footnotes................ AA CC R1 DPV false positive indicator.........
Residential delivery indicator...... N LACS-Link ind / return code.......
Occupancy code...................... Suite-Link ind / return code......
Business/residential indicator...... Record type / default flag......... S
PMB designator / number.. Street match lev / sec adr flag.... S N
looks good to me.
the second address does not validate. there is no main st. there is a main ave, but the odd number addresses start at 127.
so, again UPS is utilizing the USPS database, and the odds that their coding is wrong is minimal. which is why we need to see the logs to interpret the problems.
best.
Re: UPS XML: Support Thread
I appreciate the help. I thought the 2nd address might be invalid since I was going from a guess. The 1st, I know is correct because it is mine.
Regarding what is being transmitted, I havent a clue other than the data the upsxml mod pulls from the DB. I think that is the first part of the ups debug.... it has LA in it. Hmmm. TNX. Something for me to look at in the morning.