You gotta help a user out a little, especially if the error is catastrophic. In the case of this ridiculously cryptic error message, it is indeed catastrophic, since the user is barred from logging in, and is absolutely stuck. I’ve seen this one before*, but managed to get a snap of it this time since it was in a VM:
Well, now what? No help, no explanation, nothing. How do I fix this? What the hell is a trust relationship with a primary domain, anyway? There’s zero excuse for this abysmally terrible experience. Since I’m getting a friendly (heh) error string, not something like “Error 3X98C4” or “Fatal error in com.microsoft.security.DomainTrustController“), obviously someone bothered to write the string, associate it with the error and localize it. Why, then, isn’t there any information on what the causes might have been and (more importantly) what to do to fix it? Initially, I had no idea what to do, but learned through trial-and-error that logging in as Administrator and restarting solves it. Why does that work? No idea. How can I prevent this error in the future? Again, can’t say.
In general, I’m not a fan of help text. Nobody reads it, it’s often poorly written and an afterthought. However, in this case, there’s no alternative (i.e. a web search) to get the info.
*=And before you think this is a Server problem, and therefore not worth friendly user assistance, I’ve had it happen on Vista as well.








