BUG: Already Present Counter Not Used in SQL Security Manager

Last reviewed: April 9, 1997
Article ID: Q158606

The information in this article applies to:

Microsoft SQL Server, versions 6.0 and 6.5

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 : kbbug6.00 kbbug6.50 kbinterop kbnetwork SSrvAdmin
Version : 6.0 6.5
Platform : WINDOWS

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: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.