BUG: Error 3307 Creating sproc or view with Existing Name

Last reviewed: April 9, 1997
Article ID: Q153995
The information in this article applies to:
  • Microsoft SQL Server versions 6.0 and 6.5

SYMPTOMS

If a database is in single-user mode, then an attempt to create a stored procedure (sproc) or view with an existing name causes error 3307.

In SQL Server 6.0, the following warnings are posted in the error log:

   Error : 3307, Severity: 21, State: 1

   spid9    Process 9 was expected to hold logical lock on page 8.

   spid9    WARNING: Pss found with open sdes;  pspid 9, psuid 1, pcurdb 5,
   system table entry 0, sdesp 0xb2abc0,   objid 8

   spid9    WARNING: Pss found with open sdes;  pspid 9, psuid 1, pcurdb 5,
   system table entry 1, sdesp 0xb29ea0,   objid 3

   kernel   WARNING: Process being freed while holding Dataserver semaphore

In SQL Server 6.5, the application log of the Windows NT event viewer is filled up with 3307 error messages.

The server becomes very unresponsive and any attempt to kill the offending query fails.

WORKAROUND

To solve this problem, try canceling the query or killing the spid. If that does not help, recycle SQL Server.

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.


Additional query words:
Keywords : kbbug6.00 kbbug6.50
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.