ACC: Cannot Connect to SQL Server w/ NetWare Under Workgroups

Last reviewed: May 20, 1997
Article ID: Q90151
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0
  • Microsoft Windows for Workgroups version 3.11
  • Microsoft SQL Server version 4.2 for OS/2

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

You are unable to communicate with SQL Server in Microsoft Access when you are running Microsoft Access under Microsoft Windows for Workgroups on a Novell NetWare network.

CAUSE

The Windows for Workgroups IPX/SPX driver (MSIPX.COM) does not work correctly with Novell's named pipe requester (DOSNP.EXE) to connect to or communicate with SQL through named pipes.

RESOLUTION

Use the NetWare Integration Kit (NIK), which provides native SPX/IPX connectivity to SQL Server. This connectivity eliminates the need for DOSNP.EXE. The NIK enables Microsoft Access and Windows for Workgroups to communicate correctly with SQL Server on a Novell network.

You can obtain the NIK by purchasing SQL Server for OS/2 version 4.2B or the upgrade kit from the usual retail channels.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows for Workgroups version 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Novell's implementation of IPX is a file called IPX.COM. Microsoft's equivalent NDIS-compliant implementation of IPX is a file called MSIPX.COM, which is used by Microsoft Windows for Workgroups. MSIPX.COM is functionally equivalent to Novell's IPX.COM, but has the additional capability of using NDIS-compliant network adapter drivers.

When you install the NetWare Named Pipe Requester, a terminate-and-stay- resident program (TSR) called DOSNP.EXE installs in memory. This TSR works with IPX.COM to provide named-pipe functionality (which is the communication protocol used by SQL Server) to applications. However, DOSNP.EXE does not work correctly with MSIPX.COM at this time. Because Windows for Workgroups uses MSIPX.COM, the NetWare Named Pipe Requester does not work with Windows for Workgroups. Therefore, Microsoft Access is not able to properly communicate with SQL Server.

REFERENCES

For more information about client/server connections between SQL Server and Windows for Workgroups clients, please see the following article here in the Microsoft Knowledge Base:

   ARTICLE-ID: Q107494
   TITLE     : INF: Connecting to SQL for Windows NT from Netware Clients

NetWare is manufactured by Novell, Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.


Additional query words: importing exporting attaching
Keywords : kb3rdparty OdbcOthr
Version : 1.0 1.10 2.0
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : Info_Provided


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