Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/100818

From BetaArchive Wiki



BUG: RETURN Statement After an RPC Causes Extra Result Set

Last reviewed: April 28, 1997
Article ID: Q100818

The information in this article applies to:

  • Microsoft SQL Server version 4.2 for OS/2

BUG# OS/2: 1724 (4.2)

SYMPTOMS

An extra result set is returned from SQL Server when a stored procedure containing an EXECUTE of a remote stored procedure, followed by a RETURN statement, is executed. This does not happen if there is no return statement following the execute of the remote stored procedure, or if a local stored procedure is executed instead of a remote one.

For example, executing the following stored procedure replicates the above problem:

   create proc rpcproc as
   execute <remote machine>...sp_who
   return
   go
   execute rpcproc
   go

WORKAROUND

Modify the stored procedure, if possible, to avoid the explicit RETURN statement following the call to execute the remote stored procedure. Also ensure your front-end application is handling the extra result set properly. A DB-LIBRARY (db-lib) front-end should always call dbresults until it returns NO_MORE_RESULTS.

STATUS

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



Additional query words: RPC dbresults dblib

Keywords : kbbug4.20 kbprg SSrvServer
Version : 4.2
Platform : OS/2


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