BUG: Already Present Counter Not Used in SQL Security Manager
Article ID: 158606
Article Last Modified on 10/16/2003
APPLIES TO
- Microsoft SQL Server 6.0 Standard Edition
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q158606
BUG #: 16059 (6.5)
15654 (6.0)
SYMPTOMS
When updating logins for a Windows NT group from SQL Security Manager, the
following error is generated for each user ID that already exists in the
syslogins table:
sp_addlogin: The login <User ID> already exists
Instead of incrementing the Already Present counter in the Add SQL Login
IDs window, the Errors counter is incremented, but the Already Present
counter is set to 0 (zero). The already existing logins are not updated by
this process; they still have the same date/time stamp as the creation date.
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.
MORE INFORMATION
This problem does not occur in SQL Server 4.21a and all of its service
packs.
Additional query words: Update integrated mixed counters
Keywords: kbbug kbinterop kbnetwork KB158606