Any resolution on this yet?

The problem is logged as a defect and development is investigating.

Dave,

We brought this issue up over a month ago now, and it's costing us sales. Can you at least give us some kind of time frame? As you can imagine, it's a serious issue for us.

David

Unfortunately I can't. In my testing it appears to be happening (over the course of a week) about 0.9-1.2% of the time. My testing isn't exactly a real world scenario, because I can't constantly hit your shipping rates without impacting the performance of your site and/or irritating FedEx. We are testing some changes in a new build that may resolve this issue, but no, I can't provide a timeframe for a fix. If I test this new build and it appears to resolve the issue, then we would of course push the changes out as soon as possible.

Thanks

Are you testing on a V4 site as well? This did not happen for us before we migrated. I've seen it 3 times just this morning myself.

The integrations from v4 and v7 are completely different so the results would not be the same. Best thing I can recommend is if you want to guarantee that your user gets a shipping method right now is to have a custom shipping method. The reason for this also is say the carrier's (UPS, FedEx, USPS) servers were down, this same thing could happen...

Joe

You've seen it happening on the version 4 store? That would be unrelated to migration as we work from a backup of your site without touching the actual.

No, I'm saying back when we were on V4, we used FedEx as well and this never happened. We starting experiencing this the very first week we migrated over to V7.

Ok, that is what I've been testing.

Dave,

I'm not sure why you're only getting this around 1% of the time. It happens to me at least 1 out of every 3 tries. It actually SEEMS like most of the time I take a call to get a shipping rate I have to refresh in order to get it to work. And nearly every day I'm having a customer call asking why I don't ship to them. Fortunately since I've got a Christmas site this isn't my busy season. If this were happening in October/November/December it would be an absolute disaster. I really hope this problem is getting the attention it deserves. It really needs to get fixed, now.

David

Like I said, I can't run constant tests. Out of over 8000 rate requests I ran on your site over the course of 7 days, there were 82 failures. I'll update the thread with more information when there is information to give. Until that point, every reply to this thread is sending me an email, so I'd appreciate some patience unless there is new information. We realize this fix is important.

Thanks

I also posted this in a thread I started this morning about this error. Sorry for the duplicate, but I thought it was worth posting this here also. I set up shipping in my V7 and tested an order to my own home address. Got the dreaded error. I hope this gets fixed urgently...and I do appreciate the urgency from the Netsol team. I dont use Fed Ex - I use UPS and USPS. I have a client (www.ecostoreusa.com) that has gotten the error with Fed Ex during pre-launch testing.
(IMG:http://www.thinqdesign.com/error/error-page.gif)

I'm having the same problem with "Estimate Shipping". Shipping is enabled, UPS Online Tools is registered and enabled. Continue to receive "Shipping Not Available", whether it's in the right hand column or in the shopping cart.

Harry

Hey Dave.
Your last response was 9 days ago. Can we please have an update on this issue?
Your help is appreciated.

We are still investigating and testing ways to make the connection more reliable. I don't have any updates other than that. I haven't forgotten about the problem.

NetSol

This may be due to the fact V7 appears to be rounding weights down?
We are working with FedEx and the XML file and the tests we did this am show the Cart XML weight to be 0 pounds on items under a pound and thus no rates coming back!

So they concluded at least on our cart XML export this was happening.

Dave

While there may be a problem with the XML export, a zero weight does not cause a rate request to fail so I don't believe this to be related.

When we tested this a few minutes ago with FedEx rates did not come back.?
At least is what the Fedex Intregration told me?
And no rates appeared on our FedEx computer on the ones with no weight after we imported some orders from the migrated v7 xml into it
Dave

There is a difference between not getting a rate and a rate request failure. Not getting a rate means no rate was returned, which may happen due to weights. By failure I mean that there was an error attempting to get a rate, which is what this thread is about.

Ok Dave thanks and Sorry
Can you open a ticket about the cart rounding down the weights.
As I see in v7 XML export XML 8.5 pounds went to 8 and under 1 goes to zero

Dave

I will check it out and log if it isn't already logged.

I was having the problem with UPS where the estimated shipping was showing "Not Available", and in the checkout it showed "Shipping Not Available To This Location". After hours of trial and error, I discovered that it only happened on items listed under 1 pound. If an item showed "0" pounds and let's say 10oz, I would get the errors. Apparently the ounces weren't being rounded up to the next pound. After making the changes, it seems to be working OK. Not sure about FEDEX or USPS as I'm currently not using those options. Hope this helps...

Harry

I have been reading these posts over the last few weeks and find it odd that we are APPARENTLY NOT having this problem. (We haven't got calls from customers on it and we don't have an unusual number of abandoned carts.)

One thing I noticed is that a lot of the posts mention the side column shipping estimator. We have that turned off because it almost always returns $5.00, which is what we charge our customers using their own FedEx number. This is nowhere near what people will be charged in almost all cases AND customers really want to see all their shipping options, not just the lowest rate, not knowing what service the rate gets them. So we don't use it.

But I'm wondering if there is a connection between us not using the side column estimator and us apparently not seeing this problem. If everyone having this problem is using the side estimator, it might give NS a hint as to where to look for a possible bug fix.

Just a thought....

Hilary
www.sundialwire.com

I'm not having the problem nearly as much as previously. But in any case, I've never used the side column estimator.