• Toll-free  888-665-8637
  • International  +1 717-220-0012
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

tappedtech
#1 Posted : Wednesday, May 24, 2017 5:39:51 PM(UTC)
tappedtech

Rank: Member

Joined: 11/21/2014(UTC)
Posts: 66

Requestes via WSDL generated object to WebServices3 for ShippingRates started failing. This request worked previously:

WebServices3.ShippingRate[] shippingRates = ws.Orders_Order_FindAvailableShippingRates(ref token, order);

I updated the WebServices3 WSDL generated classes and the request still failed. This was the only shipping related change I saw (ShippingRate):
Previous: <s:element minOccurs="0" maxOccurs="1" name="SuggestedPackages" type="tns:ArrayOfPackage" />
Current: <s:element minOccurs="0" maxOccurs="unbounded" name="SuggestedPackages" type="tns:Package" />

I monitored the request and response in Wireshark. The request appears to adhere to the WebServices3 Orders_Order_FindAvailableShippingRates spec. The web service response was:
500 Internal Server Error
Server was unable to process request.
There was an error generating the XML document.
The type StructuredSolutions.Bvc5.Shipping.ExtendedShippingPackage was not expected.
Use the XmlInclude or SoapInclude attribute to specify types that are not known statically.

I checked the request and ExtendedShippingPackage doesn't exist.

Any suggestions on how to fix this?
Aaron
#2 Posted : Thursday, May 25, 2017 1:50:52 PM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
Were any changes made to the shipping methods?
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
tappedtech
#3 Posted : Friday, May 26, 2017 3:36:00 PM(UTC)
tappedtech

Rank: Member

Joined: 11/21/2014(UTC)
Posts: 66

No changes were made.
Aaron
#4 Posted : Thursday, June 1, 2017 8:12:24 AM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
Originally Posted by: tappedtech Go to Quoted Post
No changes were made.

That seems unlikely. The error indicates that one or more of the shipping methods is using one of the Shipping Rate Rule Provider methods (i.e. Order Rules, Packaging Rules, or Wrapper). It doesn't look like these methods are currently compatible with the API.
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
tappedtech
#5 Posted : Friday, June 2, 2017 2:19:53 PM(UTC)
tappedtech

Rank: Member

Joined: 11/21/2014(UTC)
Posts: 66

There are two shipping methods with Shipping Rate Rule Provider methods.

The error is still occurring after deleting the two shipping methods.
Aaron
#6 Posted : Friday, June 2, 2017 3:59:26 PM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
If you're still getting the error then there is still one or more SRRP methods (i.e. Order Rules, Packaging Rules, or Wrapper) still being used.
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

©2024 Develisys. All rights reserved.
  • Toll-free  888-665-8637
  • International  +1 717-220-0012