BUG: SEM Incorrectly Reports 4601 on Same-Named Objects

 Last reviewed: May 5, 1997
Article ID: Q152111
The information in this article applies to:
  • Microsoft SQL Server, version 6.0

SYMPTOMS

When assigning permissions on an object you own, SQL Enterprise Manager (SEM) returns error 4601: 

   Only owner <%.*s> of object <%.*s>,in database %.*s can GRANT/REVOKE
   this permission.
This situation is transient and arises when multiple objects having the same name, but different owners, are created within a database while a connection to the server is active through SEM. The user logged on to the server through SEM must be one of the owners of the objects and must sort higher alphabetically than the other object owner. When SEM is used to modify the "By User" permissions for the object owned by the user logged on, error 4601 is reported.

WORKAROUND

SEM will properly assign permissions if the connection to the server is reestablished (Disconnect and expand the server to reconnect).

You can also use the Query Analyzer to execute the T-SQL commands to grant and revoke permissions.

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: Enterprise Manager SEM permission
Keywords : kbbug6.00
Version : 6.0
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: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.