BUG: CURSOR_CLOSE_ON_COMMIT Stops SQL Enterprise Mgr. Logins

Last reviewed: April 10, 1997
Article ID: Q154889

The information in this article applies to:

Microsoft SQL Server, version 6.5

SYMPTOMS

If an SA turns on CURSOR_CLOSE_ON_COMMIT at the system level, all attempts to connect to SQL Enterprise Manager fails and the following error message appears:

   A connection could not be made to SERVERNAME - [SQL Server]
   cursor is not open.

The following syntax is used to turn on CURSOR_CLOSE_ON_COMMIT:

   sp_configure "user options", 4
   go
   reconfigure
   go

STATUS

Microsoft has confirmed this to be a problem in the Microsoft SQL Server version 6.50.201. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: 6.50.201 configure
Keywords : kbtool SSrvEntMan
Version : 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 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.