BUG: Security Manager Fails With Error 1332 Granting Logins

 Last reviewed: May 2, 1997
Article ID: Q150462

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG#: 13034 (6.00)

SYMPTOMS

When you use SQL Security Manager or the extended stored procedure xp_grantlogin to grant logins, you can receive the following error: 

   Unable to lookup account. LookupAccountSid LookupAccountSid: error 1332
   on line 1697. No mapping between account names and security IDs was
   done.

CAUSE

If a global group is granted access to SQL Server, the following situations could cause the account to become unknown:

  1. NETLOGON problems.
2. The global group is from a trusted domain and the trust relationship is 
   broken.
3. The SQL Server is running on a member server and the computer's domain 
   is changed to a workgroup or another domain.

WORKAROUND

In the Registry Editor (REGEDT32.EXE) on the SQL Server computer, look at permissions for the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer and if any unknown accounts have any permission (shown by an icon with people and question marks), delete the permission for the unknown accounts.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: xp_grantlogin xp_revokelogin SQSECMGR
Keywords : kbbug6.00 kbsetup SSrvAdmin SSrvStProc
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.