Yes, the problem is about SID translation. I can acquire SID but translation
into an NTAccount fails.
BTW, I can see actual value in Windows Explorer.
If the SID is local to the machine that it is coming from, then that might
explain it. The current machine may have no way to determine who that user
is. I can't explain why Windows explorer would be able to do it as they
should be using the same APIs, but sometimes things aren't that obvious.
What is the SID in this case? Does it belong to a specific local machine
user?
Joe K.

Signature
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
> Yes, the problem is about SID translation. I can acquire SID but
> translation into an NTAccount fails.
[quoted text clipped - 38 lines]
>>>
>>> Thanks
Dmitry Nogin - 31 Jan 2007 10:05 GMT
I checked all the possible situations:
BULTIN\Administrator
MYDOMAIN\Administrator
etc...
Sometimes it works, sometimes - no. I couldn't find any dependancy on the
origin of the account.
> If the SID is local to the machine that it is coming from, then that might
> explain it. The current machine may have no way to determine who that
[quoted text clipped - 49 lines]
>>>>
>>>> Thanks
Joe Kaplan - 31 Jan 2007 14:58 GMT
I honestly don't know. It is a generally good idea to trap the exception
returned when trying to convert between a SID and NTAccount though, as that
can fail unexpected for a variety of reasons. Sometimes you can only ever
get the original SID.
Joe K.

Signature
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
>I checked all the possible situations:
> BULTIN\Administrator
[quoted text clipped - 57 lines]
>>>>>
>>>>> Thanks