Comments on: UPS WorldShip crashes caused by new version of MySQL ODBC driver

By: Brian C.

Brian C. — Fri, 27 Nov 2009 13:06:11 +0000

Great information! This is exactly what I needed. The UPS tech guy(Tier 1) had NO clue that exporting into MYSQL from Worldship was even possible. After finding this fix I was able to connect to my database and export the tracking number.

Thanks!

By: Will W.

Will W. — Fri, 07 Aug 2009 06:52:23 +0000

We had figured this out on our own after about a half hour of troubleshooting (everything in WorldShip worked great until we tried doing exports). Retroactively searching to see if this was us or WorldShip at fault, glad to see we’re not the only ones!

By: Curtis Gibby

Curtis Gibby — Fri, 10 Jul 2009 12:35:05 +0000

Actually, Matt, I just wrote the post a few weeks ago, and since the very next day I’ve been getting consistent traffic from Google for several related keywords (like “worldship mysql 5.1 odbc” in your case).

I was just waiting for someone to chime in, saying that my solution fixed their problem too.

(Matt’s comment came from an @ups.com email address, so I’m glad that it’s helping regular people and UPS tech support folks.)

By: Matt

Matt — Fri, 10 Jul 2009 08:40:21 +0000

Great information Curtis! I only wish it had higher search index values so that I could have found it sooner. I had a customer who’s Worldship kept crashing each time we tried to make an export map. They had installed version 5.1 before I got involved and I had no reason to think that was the issue. And, like the rest of the world has found, the Worldship helpdesk just said it must be an ODBC issue and couldn’t help any more than that. I un-installed the 5.1 driver and installed 3.5 driver and viola, it works! Many thanks…