by Michael S. Kaplan, published on 2007/03/27 08:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/03/27/1961293.aspx
This is truly the error message of the week....
I could also just stop messing with servers before I try to log into them, but what fun would that be? :-)
This post brought to you by 0 (U+0030, a.k.a. DIGIT ZERO)
Rosyna on 27 Mar 2007 10:13 AM:
But how does something error and completely successfully? Hmm, unless either GetLastError() wasn't set or wasn't read and the programmer grabbed the localized value for no error (0)?
Michael S. Kaplan on 27 Mar 2007 10:38 AM:
I am guessing the former -- GetLastError() wasn't set but they blindly got the string for the error to display the reason for the failure....
I think the param is ignored in Vista/LH Server for mstsc /console since nothing runs in session 0 any more. So we might be safe from this problem now. :-)
Dean Harding on 27 Mar 2007 10:14 PM:
Actually, more likely I would say is that GetLastError WAS set, but something else set it back before it was read.
Steve Novoselac on 27 Mar 2007 11:30 PM:
hehe, i got this way back in 2004, just wacky
go to newer or older post, or back to index or month or day