Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: USPS RTShipping Timeout issue

  1. 07-12-2011, 01:13 PM #1
    sduffy77 is offline Senior Member
    Join Date
    Feb 2010
    Location
    Lancaster, PA
    Posts
    142

    Angry USPS RTShipping Timeout issue

    We're starting to see this error alot:
    Page URL:/checkout1.aspx
    Source:System
    Message:Unable to connect to the remote server
    Stack Trace:
    at System.Net.HttpWebRequest.GetResponse()
    at AspDotNetStorefrontCore.RTShipping.GETandReceiveDa ta(String Request, String Server) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\RTShipping.cs:line 3106
    at AspDotNetStorefrontCore.RTShipping.USPSGetRates(Sh ipments AllShipments, String& RTShipRequest, String& RTShipResponse, Decimal ExtraFee, Decimal MarkupPercent, Decimal ShipmentValue, Decimal ShippingTaxRate) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\RTShipping.cs:line 2128
    at AspDotNetStorefrontCore.RTShipping.GetRates(Shipme nts AllShipments, String Carriers, ResultType ListFormat, String FieldName, String CssClass, Decimal ShippingTaxRate, String& RTShipRequest, String& RTShipResponse, Decimal ExtraFee, Decimal MarkupPercent, Decimal ShipmentValue, CartItemCollection thisCart) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\RTShipping.cs:line 705
    at AspDotNetStorefrontCore.ShoppingCart.GetRates(Addr ess shipmentAddress, Decimal ShippingHandlingExtraFee) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\ShoppingCart.cs:line 7249
    at AspDotNetStorefrontCore.ShippingCalculation.UseRea lTimeRatesShippingCalculation.GetShippingMethods(I nt32 storeId) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\ShippingCalculation\UseRealTime RatesShippingCalculation.cs:line 39
    at AspDotNetStorefrontCore.ShoppingCart.GetShippingMe thods(Address usingThisAddress, Decimal taxRate) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\ShoppingCart.cs:line 3587
    at AspDotNetStorefrontCore.ShoppingCart.GetShippingMe thods(Address usingThisAddress) in C:\Projects\DOTNET\AspDotNetStorefrontMultistore_9 .1.0.1\ASPDNSFCore\ShoppingCart.cs:line 3472
    at AspDotNetStorefront.checkout1.PopulateShippingMeth ods() in e:\inetpub\wwwroot\websites\HKAndersonMS\checkout1 .aspx.cs:line 85
    at AspDotNetStorefront.checkout1.OnInit(EventArgs e) in e:\inetpub\wwwroot\websites\HKAndersonMS\checkout1 .aspx.cs:line 77
    at System.Web.UI.Control.InitRecursive(Control namingContainer)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    First is anyone else experiencing this and is there a workaround?
  2. 07-12-2011, 03:58 PM #2
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    I haven't had any other reports of anything like that today, which we generally would if one of the carriers was down. Sounds like it's most likely a routing issue. I would get the URL for the shipping carrier service from the AppConfigs (the config name will depend on the carrier you're using, but if you look at the AppConfigs for your carrier you'll see it) and then check with the host, and make sure that address is reachable from the server your site's on.
    ECommerce Shopping Cart
  3. 07-21-2011, 10:59 AM #3
    sduffy77 is offline Senior Member
    Join Date
    Feb 2010
    Location
    Lancaster, PA
    Posts
    142

    Default

    We've figured it out.

    Turns out the USPS url is using multiple IPs. When our network tech added the firewall rule to allow communication they only entered the one IP.

    We're good now.