FIX: Passing a Large Command Line String to Query Analyzer Results in Assertion Failed
This article was previously published under Q294828
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 353011 (SHILOH_BUGS)BUG #: 353081 (SHILOH_BUGS)
When you start Query Analyzer (Isqlw.exe) from a command prompt and attempt to pass a very long string (around 1370 characters) using the /U parameter, an error message that resembles the following may be displayed:
[Microsoft][ODBC Driver Manager]Data source name not found and no default driver specified
After you click
, or press ESC, the
Connect to SQL Server
dialog box is displayed. At this point, you have the following options:
If you click Cancel, or press ESC, you receive the following error message:
Assertion Failed!If you then click
Program: ...s\Microsoft SQL Server\80\Tools\BINN\isqlw.exe File: ..\src\comboex.cpp Line: 806 Expression: 0 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) Abort, you are returned to the command prompt. If you click Retry or Ignore, the following dialog box appears:
Program ErrorYou must then click
isql.exe generated errors and will be closed by Windows. You will need to restart the program. An error log is being created. OK, and you are returned to the command prompt. If you enter valid SQL Server authentication credentials or switch to Windows authentication, the following dialog box appears:
SQL Query AnalyzerAt this point, you must click
Unable to connect to server <servername>: ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified OK, or press ESC, and you are returned to the Connect to SQL Server dialog box.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
INF: How to Obtain the Latest SQL Server 2000 Service Pack
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
Article ID: 294828 - Last Review: 01/16/2015 22:11:25 - Revision: 3.2
Microsoft SQL Server 2000 Standard Edition
Keywords: kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB294828