RTR not working.

[turbo2ltr]

This is a new installl.
Cart works fine until you after you fill in your ship/bill address. Then it either comes up with a blank "main content' area, or it says
A default shipping method of ($) has been added to your order.

I am registered for both UPS and USPS RTR.
I have confirmed that CURL and OpenSSL are working via the test page (diag_curl.php)
My one product had full dimention and weight info filled in
My store info is set complete with state and zip and I even added a second warehouse to make sure.
I have no rules enabled as per http://www.squirrelcart.com/help/1.5.0/?4.4.3.1.5
(I did my homework before posting)

This is really starting to get on my nerves. Is there no way to get diagnostic information from the RTR requests? A blank page or an empty 'default' shipping method sounds like not enough error checking is being done. Enabling the diagnostic mode gives no information in the popup other than "no discount found".

Without RTR, is there a way to allow the user to choose a ship method? Or does it automatically pick using the rules? So far in all my testing, the cart has never prompted me to pick a shipping method. It has always applied a default.

[turbo2ltr]

Got this back after enabling some debug lines that were commented:

<accessrequest xml:lang="en-US">
<accesslicensenumber>[removed]</accesslicensenumber>

<userid>[removed]</userid>
<password>[removed]</password>
</accessrequest>

<?xml version="1.0"?>
<RatingServiceSelectionRequest xml:lang="en-US">
<Request>

<TransactionReference>
<CustomerContext>Bare Bones Rate Request</CustomerContext>
<XpciVersion>1.0001</XpciVersion>
</TransactionReference>
<RequestAction>Rate</RequestAction>
<RequestOption>Rate</RequestOption>
</Request>

<PickupType>
<Code>01</Code>
</PickupType>
<Shipment>
<Shipper>
<Address>
<PostalCode>85022</PostalCode>
<CountryCode>US</CountryCode>

</Address>
</Shipper>
<ShipTo>
<Address>
<PostalCode>85085</PostalCode>
<CountryCode>US</CountryCode>
<ResidentialAddressIndicator>1</ResidentialAddressIndicator>

</Address>
</ShipTo>
<ShipFrom>
<Address>
<PostalCode>85022</PostalCode>
<CountryCode>US</CountryCode>
</Address>
</ShipFrom>

<Service>
<Code>03</Code>
</Service>
<Package>
<PackagingType>
<Code>02</Code>
</PackagingType>
<PackageWeight>

<UnitOfMeasurement>
<Code>LBS</Code>
</UnitOfMeasurement>
<Weight>3</Weight>
</PackageWeight>
</Package>
</Shipment>
</RatingServiceSelectionRequest>

<------------------

<RatingServiceSelectionResponse>
<Response>
<TransactionReference>
<CustomerContext>Bare Bones Rate Request</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>
<------------------


There were more (assuming for the different ship methods) and they all had the same error response. So what does this mean and why isn't it working?

edit: snipped xml wasnt formed right...

[Rich]

Hello,

Please open a ticket with our help desk and we'll look into this for you.
http://www.ldev.com/helpdesk/You'll need to register for a help desk account if you haven't already done so.

[turbo2ltr]

Are the accesslicensenumber, userid, and password supposed to be a bunch of extended characters?

[turbo2ltr]

After way too much troubleshooting I narrowed it down..

It has something to do with mcrypt on IIS. The decrypt isn't failing (and AFAIK, it is installed correctly on the server) but it is not decrypting correctly. If I force the UN, PW, and AL in the code to the correct plaintext, the request goes through. The error was generated because of the extended characters in the XML (where the decrypted info should have been) which I belive violates the spec. So if anyone is dealing with the "XML Not well formed" error, take a look and make sure there aren't any extended characters in the string.

It does however work on on the linux server which is where it will eventually end up, so I can deal with that.

[Webmaker]

I'm experiencing the same problem. :confused: Was this ever answered, or do I need to submit a helpdesk ticket?

[turbo2ltr]

It was never looked into as I was only testing on IIS locally. My real web host runs linix so I didn't persue it.

[Rich]

I'm experiencing the same problem. :confused:Actually, the issue you were experiencing was quite different. I've responded to your help desk ticket with more information.