Re: You Can't Spell "Stupid..."



On Wed, 28 Dec 2005 09:06:55 -0600, Dave Buckles
<dbuckles@xxxxxxxxxxx> wrote:

>FedEx, of course, sucks too, I just haven't figured out how yet.

::delurk::

I have, at home in the closet, one FedEx polo shirt that was one of
the freebies lavished upon myself and a handful of others as a result
of their monumental screwage.

Step one: have FedEx Freight pick up one fully-loaded HP NetServer, at
the time a $70K piece of kit, to be delivered tout-suite to fl.us from
md.us in order to be available for an install in two days. Pay
$bignum for this to occur, guaranteed, with damage insurance. Watch
crate and pallet disappear into the back of the Big White Truck.

Step two: board plane to FLL from BWI two days later. Arrive in FLL
in late morning and drive to site to find... a remarkably empty space
where the server should be. It was so bereft of server, you could eat
from it.

Step three: call FedEx. Find out that the server is sitting in the
cargo depot in Newark, NJ. Inquiries as to why were not met with
anything approaching an explanation. Request crate be put on
afternoon flight to MIA and couriered to site.

Step four: shortly thereafter, receive call from FedEx rather
curiously hinting that they might not be able to find our server after
all. Suggest they check behind the couch.

Step four-and-a-half: hours later, receive call from FedEx rep
explaining that transport to MIA would be impossible, since crate
(upon being discovered on the dock in Newark) had been loaded into the
back of a truck to be driven down I-95. No way to recall in time to
make the afternoon MIA flight.

Step five: ??? Involved leaving site and getting smashed.

Step six: Show up at site next morning to wait for four and a half
hours for the courier to arrive late with the server. Damaged.

Fortunately, the damage was confined to the lower drive cages for the
data volumes, and the mirrored set for the OS was fully functional.
At least I got to install and configure the <gnash teeth> SCO
OpenServer slop while waiting for the replacement bits from local HP
guys to brain-swap the drives into. Realize it would have been faster
and just as expensive to just have bought the new box from them the
day before.

Again fortunately, this was all on the client's dime and they got to
pay me for 12 hours of sitting in the conference room listening to
them scream into a phone at FedEx Customer Disservice. At $120 per.
I've no idea how much of that the client was able to recoup. But I
got a nice, grey polo.

--
Strange, Geometrical Hinges: http://rob.rnovak.net
.



Relevant Pages

  • Re: How to avoid the spam on this news group?
    ... each participating server actually has local copies of all ... USENET is a like a bookstore, HTTP is like FedEx. ...
    (comp.unix.programmer)
  • WSDL+SOAP get resulting Xml
    ... Fedex in the US is changing their method of dealing with their servers for ... The old method was a formatted Xml file ... You then parsed the returned Xml that contained ... the actual SOAP message that I send and also their server response. ...
    (microsoft.public.dotnet.languages.vb)
  • SOAP xml
    ... The old method was a formatted Xml file submitted via an HTTP Post. ... You then parsed the returned Xml that contained the information requested. ... However I have a problem when I deal with Fedex tech support when I have questions about some of their other services, ... I understand basically what is happing with the WSDL and the SOAP message that is actually created and sent to their server, but I don't know how to access the actual XML that is sent/received to Fedex. ...
    (microsoft.public.dotnet.xml)
  • Re: Moving databases across network
    ... Fedex will beat ... any pipe with that size of data. ... Mike Epprecht, Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.server)