Knowledge Base

BUG: Failed SQL Server RPC Call Results in Batch Termination

Article ID: 165132

Article Last Modified on 10/3/2003

APPLIES TO

This article was previously published under Q165132
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: kbbug kbusage KB165132


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.