BUG: Security Manager Fails With Error 1332 Granting Logins (150462)
The information in this article applies to:
- Microsoft SQL Server 6.0
- Microsoft SQL Server 6.5
This article was previously published under Q150462
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:
- NETLOGON problems.
- The global group is from a trusted domain and the trust relationship is
broken.
- 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. To
see these permissions, select the key listed above and click Permissions
on the Security menu.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
versions 6.0 and 6.5. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
| Modification Type: | Minor | Last Reviewed: | 3/14/2005 |
|---|
| Keywords: | kbbug kbsetup KB150462 |
|---|
|