Microsoft KB Archive/267550

= BUG: &quot;Assertion Failed&quot; When You Connect to a SQL Server Through TCP/IP =

Article ID: 267550

Article Last Modified on 2/12/2007

-

APPLIES TO


 * Microsoft ODBC Driver for Microsoft SQL Server 3.7
 * Microsoft OLE DB Provider for SQL Server 7.0
 * Microsoft OLE DB Provider for SQL Server 7.01
 * Microsoft Data Access Components 2.1
 * Microsoft Data Access Components 2.5
 * Microsoft Data Access Components 2.6
 * Microsoft Windows 98 Standard Edition

-



This article was previously published under Q267550



SYMPTOMS
When you attempt to connect to a SQL Server through TCP/IP on a Windows 98 client, the following error message can occur:

Assertion failed!

Program: C:\WINDOWS\RUNDLL32.EXE

File: ../src/sqlsspi.c

Line: 120

Expression: Count

For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts

(Press Retry to debug the application - JIT must be enabled)

If you click Ignore, the following error message is displayed:

Connection failed:

SQLState: 'HY001'

SQL Server Error: 0

[Microsoft][ODBC SQL Server Driver]Memory allocation failure

Connection failed:

SQLState: 'HY000'

SQL Server Error: 8

[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context

NOTE:The first error message can be displayed with a different line number, such as Line 119 or Line 124, depending on the version of the components installed on your computer.

In the first error message, the executable that is listed after &quot;Program&quot; is the name of the application that attempts the connection. The connection is attempted from the ODBC Data Source Administrator in the Control Panel. Other common application names are the Mmc.exe file for the SQL Server Enterprise Manager, and the Isqlw.exe file for the Query Analyzer.



CAUSE
This problem occurs because the client computer does not have the Client for Microsoft Networks installed.



RESOLUTION
To resolve this problem, install the Client for Microsoft Networks as one of the networking components on the computer. The Client for Microsoft Networks does not have to be the Primary Network Logon.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
This problem has been reproduced from several clients, including the SQL Server Enterprise Manager, Query Analyzer, and both the Microsoft Open Database Connectivity (ODBC) and the OLE DB client applications.

This problem has not been reproduced on Windows 98 Second Edition.

