• Resolved musclepotential

    (@musclepotential)


    I have used this for a while and now it just stopped working. No matter what address is put in it always comes back with

    “There are no shipping methods available. Please ensure that your address has been entered correctly, or contact us if you need any help.”

    There have been no setting changes or anything else done to cause this error. I ran the debugging mode and this is what I am getting:

    USPS REQUEST:
    API=RateV4&XML=<RateV4Request USERID=”570CYDTE1766″><Revision>2</Revision><Package ID=”2e09f51fdaa390158106b874d1b98821:1:0:0:0:1″> <Service>ALL</Service> <ZipOrigination>32819</ZipOrigination> <ZipDestination>32246</ZipDestination> <Pounds>1</Pounds> <Ounces>0.00</Ounces> <Container /> <Size>REGULAR</Size> <Width>0</Width> <Length>0</Length> <Height>0</Height> <Girth>0</Girth> <Machinable>true</Machinable> <ShipDate>25-May-2018</ShipDate></Package></RateV4Request>

    USPS RESPONSE:
    <?xml version=”1.0″ encoding=”UTF-8″?>
    <RateV4Response><Package ID=”2e09f51fdaa390158106b874d1b98821:1:0:0:0:1″><Error><Number>-2147219385</Number><Source>DomPostageLibrary;RateV4.ProcessRequest</Source><Description>Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.</Description><HelpFile/><HelpContext/></Error></Package></RateV4Response>

    I am not sure what this mean???

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter musclepotential

    (@musclepotential)

    When I try to use my own Username I get this error message

    USPS REQUEST:
    API=RateV4&XML=<RateV4Request USERID=”444MUSCL6302″><Revision>2</Revision><Package ID=”2e09f51fdaa390158106b874d1b98821:1:0:0:0:1″> <Service>ALL</Service> <ZipOrigination>32819</ZipOrigination> <ZipDestination>32246</ZipDestination> <Pounds>1</Pounds> <Ounces>0.00</Ounces> <Container /> <Size>REGULAR</Size> <Width>0</Width> <Length>0</Length> <Height>0</Height> <Girth>0</Girth> <Machinable>true</Machinable> <ShipDate>25-May-2018</ShipDate></Package></RateV4Request>

    USPS RESPONSE:
    <?xml version=”1.0″ encoding=”UTF-8″?>
    <Error>
    <Number>80040B18</Number>
    <Description>An error has occurred with the service. Please contact the system administrator, or try again.</Description>
    <Source>USPSCom::DoAuth</Source>
    </Error>

    I am using another platform called Pressero and I am getting the same error message for all of my storefronts.

    If I keep trying eventually the shipping works but most of the time I get the 80040B18 error like you.

    This is the only mention of that error I could find on Google in the last 24 hours.

    Perhaps it’s a USPS issue?

    I’m havings the same error! Customer ordered and woocommerce plugin charged them the failback ($9). Run the same purchase with their address now and actual cost with priority is $19.20.

    This is really frustrating, ether I can disable failback and lose customers because they can’t order, or let this plugin give products away. I don’t get it.

    This error has happened 5 times in the last 4 days.

    05-25-2018 @ 00:16:41 – Error: Unexpected USPS Response: <?xml version=”1.0″ encoding=”UTF-8″?>
    <Error>
    <Number>80040B18</Number>
    <Description>An error has occurred with the service. Please contact the system administrator, or try again.</Description>
    <Source>USPSCom::DoAuth</Source>
    </Error> (calculate_shipping)
    05-25-2018 @ 00:18:38 – Error: Unexpected USPS Response: <?xml version=”1.0″ encoding=”UTF-8″?>
    <Error>
    <Number>80040B18</Number>
    <Description>An error has occurred with the service. Please contact the system administrator, or try again.</Description>
    <Source>USPSCom::DoAuth</Source>
    </Error> (calculate_shipping)

    Hi All,

    The USPS server seem to be down at the moment please check again later,

    If this is not fixed yet in another 12 hours do let me know.

    Regards,

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin Stopped Working’ is closed to new replies.