INF: Remote Procedure Calls with Sybase SQL Servers

Last reviewed: June 5, 1997
Article ID: Q169283
The information in this article applies to:
  • Microsoft SQL Server, versions 4.2x, 6.0, and 6.5

SUMMARY

Server-to-server remote procedure calls (RPCs) between Microsoft SQL Server and Sybase SQL Server may not work properly under certain situations. If you have gone through all the RPC troubleshooting and configuration procedures as documented in the SQL Server Books Online, but still cannot make it work properly, you should consult Sybase's product Release Bulletins for the corresponding versions of Sybase SQL Servers involved in the RPC.

MORE INFORMATION

Remote procedure calls between Microsoft SQL Servers and Sybase SQL Server version 4.x generally work fine. However, if you are using Sybase SQL Server version 10.x or 11.x, you may experience difficulties executing RPCs to or from Microsoft SQL Servers. For more information on these RPC issues, please consult Sybase's product Release Bulletins, which are typically available through Sybase SQL Server product packages, Sybase's knowledge base compact disc (AnswerBase), or Sybase's Internet Web site at http://www.sybase.com/.


Additional query words: System 10 connectivity
Keywords : kb3rdparty SSrvGen
Version : 4.2 6.0 6.5
Platform : WINDOWS
Issue type : kbinfo


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