BUG: SQL Bridge on Alt Pipe and Remote Stored Procedure

Last reviewed: April 28, 1997
Article ID: Q88086

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2

SYMPTOMS

When running SQL Server on the default pipe (\pipe\sql\query) and running SQL Bridge on an alternate pipe, an attempt to do remote stored procedures from Microsoft SQL Server to Sybase SQL Server might generate the following message:

   Can't open connection to site <servername>. See the error log
   file in the SQL Server boot directory.

And in the error log, you might find this message:

   Invalid network type ('DBMSNP') in Profile String for
   application (Server) 'SQLSERVER_<Servername>' and key
   (Service) 'Query'.

CAUSE

This problem occurs because SQL Server checks for an entry for "DBNMPP" instead of "DBMSNP" in the OS2.INI file in the following section:

   SQLSERVER_<Servername>
   QUERY:DBMSNP,<alt. pipe name>

WORKAROUND

To execute remote stored procedures from Microsoft SQL Server to Sybase SQL Server with SQL Bridge running on an alternate pipe, under the SQLSERVER_<servername> section in the OS2.INI file, use the entry "DBNMPP", as shown below:

   SQLSERVER_<Servername>
   QUERY:DBNMPP,<alt. pipe name>

You do not need to have the DBNMPP.DLL file on your machine.

STATUS

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


Additional query words: SQL Bridge
Keywords : kbbug4.20 kbother SSrvServer
Version : 4.2
Platform : OS/2
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: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.