Another Error Message That's Helpful (NOT)
-
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed". For me the #1 rule to follow with error messages is to instruct the user in how to recover. And geez, that's nice to inform me of a pipe being closed. I wonder if it needs to be lit first in order for it to work? Perhaps the coder should have used a bong instead of a pipe. :mad:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed". For me the #1 rule to follow with error messages is to instruct the user in how to recover. And geez, that's nice to inform me of a pipe being closed. I wonder if it needs to be lit first in order for it to work? Perhaps the coder should have used a bong instead of a pipe. :mad:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
But that seems like a perfectly helpful error. Personally, I dislike the following: "An error as occurred, please see error log for details. Contact support if error persists. Press OK to continue"
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed". For me the #1 rule to follow with error messages is to instruct the user in how to recover. And geez, that's nice to inform me of a pipe being closed. I wonder if it needs to be lit first in order for it to work? Perhaps the coder should have used a bong instead of a pipe. :mad:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
Did it leave you with a "Blue Screen of Like Whatever man, hey got any biscuits?":)
------------------------------------ Happy Primes Lead to Happy Memories. Don't Google FGI
-
But that seems like a perfectly helpful error. Personally, I dislike the following: "An error as occurred, please see error log for details. Contact support if error persists. Press OK to continue"
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayEnnis Ray Lynch, Jr. wrote:
But that seems like a perfectly helpful error.
I'll agree, but only in the context of the user being a developer. When the user is not a developer or any kind of technical specialist, the error message is non helpful since it explains nothing nor assists in resolving the issue. On a side note, after I clicked the OK button the application started and the view was filled with the exact same error information and a button with the title, "Click to reload". When I clicked that button, everything worked like a charm. I'd rather the initial message box contain two buttons, one to request the reload, the other to cancel or close the app.
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
Did it leave you with a "Blue Screen of Like Whatever man, hey got any biscuits?":)
------------------------------------ Happy Primes Lead to Happy Memories. Don't Google FGI
:-D :-D :-D
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
Did it leave you with a "Blue Screen of Like Whatever man, hey got any biscuits?":)
------------------------------------ Happy Primes Lead to Happy Memories. Don't Google FGI
I think I'll change my MessageBoxes to say things like: "The butterflies have gotten loose." "These pretzels are making me thirsty." "Everybody have fun tonight, everybody wang chung tonight." Etc.
-
I think I'll change my MessageBoxes to say things like: "The butterflies have gotten loose." "These pretzels are making me thirsty." "Everybody have fun tonight, everybody wang chung tonight." Etc.
And, "Party on, Garth." :cool:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed". For me the #1 rule to follow with error messages is to instruct the user in how to recover. And geez, that's nice to inform me of a pipe being closed. I wonder if it needs to be lit first in order for it to work? Perhaps the coder should have used a bong instead of a pipe. :mad:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
Chris Meech wrote:
Cannot show view information: neuron I/O error: The pipe is being closed
I sometimes get that message at the bar around closing time. A couple of Rolaids and a shot of tequila usually sets me straight. Much worse are any messages from MS, usually containing no information at all about the problem or the solution, and instructing me to see the System Administrator. I am the System Administrator, and I'm no more clairvoyant than any other user.:mad:
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
Chris Meech wrote:
Cannot show view information: neuron I/O error: The pipe is being closed
I sometimes get that message at the bar around closing time. A couple of Rolaids and a shot of tequila usually sets me straight. Much worse are any messages from MS, usually containing no information at all about the problem or the solution, and instructing me to see the System Administrator. I am the System Administrator, and I'm no more clairvoyant than any other user.:mad:
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Excellent. I know there was a good reason for keeping that Tequila around here at work. :-D
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed". For me the #1 rule to follow with error messages is to instruct the user in how to recover. And geez, that's nice to inform me of a pipe being closed. I wonder if it needs to be lit first in order for it to work? Perhaps the coder should have used a bong instead of a pipe. :mad:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
Chris Meech wrote:
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed".
I know the application. By the most improbable coincidence I got that error (first time I've ever seen it) this morning too. Let me guess: A source control application? From a Canadian vendor? Am I getting warm? I like the "neuron" bit. Make it feel like there's some AI going on in the background... Share and enjoy. Sean
-
Chris Meech wrote:
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed".
I know the application. By the most improbable coincidence I got that error (first time I've ever seen it) this morning too. Let me guess: A source control application? From a Canadian vendor? Am I getting warm? I like the "neuron" bit. Make it feel like there's some AI going on in the background... Share and enjoy. Sean
DING. DING. DING. We have a winner. :)
Sean Michael Murphy wrote:
By the most improbable coincidence I got that error (first time I've ever seen it) this morning too.
I'm beginning to thing you and I work for the same company. Let's see know, large Canadian financial institution. Can you say BANK. :-D
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
DING. DING. DING. We have a winner. :)
Sean Michael Murphy wrote:
By the most improbable coincidence I got that error (first time I've ever seen it) this morning too.
I'm beginning to thing you and I work for the same company. Let's see know, large Canadian financial institution. Can you say BANK. :-D
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
Chris Meech wrote:
I'm beginning to thing you and I work for the same company. Let's see know, large Canadian financial institution. Can you say BANK.
Yeah, I just looked you up in the enterprise directory and apparently we do share an employer. I am ashamed to say that I was an active participant in the UAT of that particular upgrade, and I gave the upgrade a lukewarm endorsement prior to it being rolled out. I didn't get that stupid error during the UAT. Not that it would have mattered, of course. We had to upgrade. The performance of the server of the old version was shameful. The new back end is supposed to be much better. Share and enjoy. Sean
-
Chris Meech wrote:
I'm beginning to thing you and I work for the same company. Let's see know, large Canadian financial institution. Can you say BANK.
Yeah, I just looked you up in the enterprise directory and apparently we do share an employer. I am ashamed to say that I was an active participant in the UAT of that particular upgrade, and I gave the upgrade a lukewarm endorsement prior to it being rolled out. I didn't get that stupid error during the UAT. Not that it would have mattered, of course. We had to upgrade. The performance of the server of the old version was shameful. The new back end is supposed to be much better. Share and enjoy. Sean
Sean Michael Murphy wrote:
Yeah, I just looked you up in the enterprise directory and apparently we do share an employer.
My, how small the CP world can really be at times. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
I won't mention the particular piece of software, but I just opened up a client application and received the following in a message box, "Cannot show view information: neuron I/O error: The pipe is being closed". For me the #1 rule to follow with error messages is to instruct the user in how to recover. And geez, that's nice to inform me of a pipe being closed. I wonder if it needs to be lit first in order for it to work? Perhaps the coder should have used a bong instead of a pipe. :mad:
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
If that one makes you unhappy, don't whatever you do buy any Adobe software. My all-time favourite Adobe error message was delivered unto me by FrameMaker, when I tried to compile a (completely black & white) document: "Color defintion for orange is inconsistent." It neglected to tell me what it was inconsistent with -- green, maybe? It took me over an hour to find out what the hell it was talking about -- ignoring error messages is rarely a wise thing to do -- only to discover that it didn't matter a jot and I should have ignored it.