Re: LookupAccountName fails with error 1332
From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 08/09/05
- Next message: Bonj: "winlogn notification package OR gina fire on "Run as..."?"
- Previous message: Matt: "Re: LookupAccountName fails with error 1332"
- In reply to: Matt: "Re: LookupAccountName fails with error 1332"
- Next in thread: Rhett Gong [MSFT]: "Re: LookupAccountName fails with error 1332"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 8 Aug 2005 17:10:50 -0500
Does it work with the full name, "BUILTIN\Server Operators"?
I'm not sure why Administrators would work without that, but who knows...
Joe K.
"Matt" <anonmous@nospam.nospam> wrote in message
news:79BFB6C1-2B76-40BB-8538-093682E04EDD@microsoft.com...
> Joe,
> Thanks for your response. That was my initial thought as well.
> However,
> the documentation for LookupAccountName states the following regarding the
> lpSystemName parameter (which is NULL in my case):
>
> If this string is NULL, the account name translation begins on the local
> system. If the name cannot be resolved on the local system, this function
> will try to resolve the name using domain controllers trusted by the local
> system.
>
> The way this reads to me is that if the local security authority cannot
> resolve it, it will try the domain controller.
>
> Matt
>
>
> "Joe Richards [MVP]" wrote:
>
>> I would guess that you aren't asking a machine that knows what server
>> operators
>> is. This name could only be resolved on a domain controller.
>>
>> --
>> Joe Richards Microsoft MVP Windows Server Directory Services
>> www.joeware.net
>>
>>
>> Matt wrote:
>> > Hello,
>> > LookupAccountName fails with error '1332' whenever I use "Server
>> > Operators" as the lpAccountName argument. This call fails on both
>> > Windows
>> > 2000 Server SP2 and SP3 systems. The same code handles
>> > "Administrators" and
>> > "System" for example with no problem.
>> >
>> > Thanks,
>> >
>> > Matt
>>
- Next message: Bonj: "winlogn notification package OR gina fire on "Run as..."?"
- Previous message: Matt: "Re: LookupAccountName fails with error 1332"
- In reply to: Matt: "Re: LookupAccountName fails with error 1332"
- Next in thread: Rhett Gong [MSFT]: "Re: LookupAccountName fails with error 1332"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|