ACC: Cannot Connect to SQL Server w/ NetWare Under WorkgroupsLast reviewed: May 20, 1997Article ID: Q90151 |
The information in this article applies to:
SYMPTOMSAdvanced: 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.
CAUSEThe 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.
RESOLUTIONUse 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.
STATUSMicrosoft 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 INFORMATIONNovell'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.
REFERENCESFor 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 ClientsNetWare 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |