Microsoft Knowledge Base Email Alertz

(267550) - 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...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 267550 - Last Review: February 12, 2007 - Revision: 4.2

BUG: "Assertion Failed" When You Connect to a SQL Server Through TCP/IP

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center
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 "Program" 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.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
229608  (http://kbalertz.com/Feedback.aspx?kbNumber=229608/EN-US/ ) BUG: SQL 7.0 Desktop Edition Install on Windows 98 Causes Assertion Failed File: ..\SRC\SQLSSPI.C Line: 119

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
Keywords: 
kbbug kbdatabase kbfix KB267550
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate