Microsoft KB Archive/254341

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:16, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


PRB: Legacy DB-Library Application May Fail to Connect After You Install SQL Server Client Tools

Article ID: 254341

Article Last Modified on 10/16/2002



APPLIES TO

  • Microsoft SQL Server 7.0 Standard Edition



This article was previously published under Q254341

SYMPTOMS

A DB-Library application that worked fine with Microsoft SQL Server 6.5 is unable to connect to Microsoft SQL Server 7.0 after you install the SQL Server 7.0 Client tools. If the client connects by using TCP/IP sockets, the Dbmssocn.dll file, the following error messages might occur:

Microsoft Visual C++ runtime library
Assertion Failed
Program: C;\Windows\MMC.EXE
File: ..\SRC\SQLSSPI.C

-or-


DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
General network error. Check your documentation.
Net-Library error 11001: ConnectionOpen (gethostbyname()())

CAUSE

The DB-Library DLL, Ntwdblib.dll, was updated to version 7.00.623 and then installed to the \Winnt\System32 directory or on a Microsoft Windows 95-based computer or Microsoft Windows 98-based computer, the \Windows\System directory, and the application using the sockets Net-Library is attempting to make a trusted connection to the SQL Server through the SSPI API even though a trusted connection was not requested.

WORKAROUND

Replace the Ntwdblib.dll with version 6.50.409 from Microsoft SQL Server 6.5 Service Pack 5a (SP5a).

MORE INFORMATION

A client computer that does not have the Microsoft Windows Network Client installed also fails to connect when you use the TCP/IP sockets Net-Library.


Additional query words: Powerbuilder Netware Intranetware Novell

Keywords: kbbug kbprb KB254341