more ungraceful failure messages

tags: , ,

Sparkle is running smoothly but there appear to be a few hiccups among the internet services Sparkle uses. Here’s a selection of recent bumps from McAfee, Optimalworkshop and SharePoint services and Oracle.com:

MacAfee providing life safety instructions instructions for life More Sharepoint Errorness Oracle Error

McAfee is just being darn mysterious. This message lead to a support call. Optimal workshop eventually provided a rather nice personable note about their server being confused, they helped their server out quite promptly. To get SharePoint access I moved to another computer which solved the problem. Oracle’s messaging reminded me of the 1980’s. I’m so glad that most of the world has moved-on. Bu would appreciate a concerted effort to start including graceful failure messages.

more ungraceful failure messages
1 vote rating 4

6 bits of lovely banter on “more ungraceful failure messages”

  1. ExpatEgghead writes:

    I agree. My failure messages alternate between being too geeky and downright condescending. I am heavily criticised at work for my failings. In my defense, I can only argue that wetware is not my specialty and we should really bring in a graphics designer and a human interaction engineer.
    I’ll stick with hardware, firmware and software hoping that I can leave the wetware to others.

       0 likes

    [reply]

  2. Nicky writes:

    Content editors! Give some web content editors the job

       0 likes

    [reply]

  3. Indigo Roth writes:

    Yes! Something like,

    “Your data is truly lost
    And Truth Is Beauty
    Enjoy the beauty of this event”

    Roth

       1 likes

    [reply]

  4. wendy writes:

    excellent. but please don’t loose my data

       0 likes

    [reply]

  5. Andrew writes:

    one of my ‘favourite’ error mesages (in part) is something along the lines of “could not create absolute affinity request”.
    There is then much other text, almost, but not quite as useful as that in understanding WTF one should do to fix/avoid this error, and also not as interesting.
    I think basically it means “We’re too busy dealing with other people’s requests for data at the moment, so can’t allocate any elastic bands to power your query right now. Please try again later.”

    I’d like it to try using relative affinity instead sometimes, but seems it never does.

    (there are some ‘interesting’ bits of GUI design in this ‘enterprise level software’ as well. I’m not going to list them here else I might start foaming at the mouth again.)

       1 likes

    [reply]

    Andrew writes

    addendum: I forgot to mention pogo sticks. For some reason they are often mentioned in the error messages from this software package as well. Maybe that’s where the elastic bands come from.

       1 likes

    [reply]

share your wonderful musings

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Anti-spam image