BUG: Failed SQL Server RPC Call Results in Batch Termination

Last reviewed: April 22, 1997
Article ID: Q165132

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG#: 16506 (6.5)

SYMPTOMS

The failed execution of a SQL Server RPC call terminates the current batch, but reports it as an informational message to the client.

STATUS

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

MORE INFORMATION

For example, if you try to run "exec RemServer.master.dbo.sp_who" and the SQL Server is not started on the RemServer, the connection returns:

   Msg 18481, Level 9, State 2
   Unable to connect to site 'RemServer' because it is unavailable or does
   not exist.

The batch is immediately terminated, so a check for @@ERROR will not even be run.

In this situation, the client receives an informational message. The DB-Library call dbsqlexec returns SUCCEED, and an ODBC SQLExecDirect reports SUCCESS_WITH_INFO.

Keywords : kbusage SSrvGen kbbug6.50
Version : 6.5
Platform : WINDOWS
Issue type : kbbug

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