BUG: Wrong Error# Trying to Connect Client to Paused SQL Svr

Last reviewed: May 2, 1997
Article ID: Q141669

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 12485 (6.00)

SYMPTOMS

When SQL Server is paused, any attempt you make to connect from a client tool, for example ISQL/W, gives the following error:

   Msg. No.: -10737; Severity: 14; State  0
   SQL Server has been paused; No new connections will be allowed.

The message number is incorrect. The correct message number should be 17142. The message defined in the source is:

   MessageID: INIT_SRVC_PAUSED
   SQL Server has been paused; No new connections will be allowed.

This is defined as 0xc00042f6. By turning on trace flag 4031 you can see that SQL Server sends the correct message number in byte-reversed order: f64200c0.

STATUS

Microsoft has confirmed this to be a problem in 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: SQL6 errmsg
Keywords : kbbug6.00 kbusage SSrvGen
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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