If you work in tech support, you may sometimes have to deal with idiots. The worst are the nitpicky jackasses that want to know exactly what an error message really means, and don't believe you when you say it doesn't matter, because after the problem isn't the error MESSAGE it's the fact that you're getting an error at all. We have a big honking database full of ways to fix the error, but WHO CARES what the message means? Not the developers - if they cared, they would have written a decent error message.
Well, for those calls there is a solution. Now, the next time you get "Error Code 643" and they demand to know what it is and why it's happening you can tell those dweebs it's because "ERROR_DS_VERSION_CHECK_FAILURE." Yes, yes, you could tell them what it really means (version incompatibility) but what fun is that? Why should you admit your lazy developer used a non-standard build to develop the application and released it to the company not realizing that the old drivers wouldn't work? Fix the problem, not the blame. Besides, it's equally likely that your dumb user decided to install some new software without approval from the IT department and it wrote over a critical DLL, and that's what's causing the error. They're not going to admit to that. You know how to fix it, and now they can bask in the knowledge of knowing what it means, and if they have half a brain, they can figure out why it happened for themselves.
Oh, by the way, it was because the dumb user had installed some software from the patent department without telling IT, and it updated a DLL which our mission-critical software, written in the dark ages, would not recognize. The solution is of course to restore the old DLL (which the new software recognized with no problem).
Leave a comment