FIX: Using DBCC Stackdump or CTRL+C + D Causes Fatal Exception on Windows 95 & Windows 98

Article translations Article translations
Article ID: 239773 - View products that this article applies to.
This article was previously published under Q239773
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53590 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

NOTE: The following DBCC command is unsupported, and may cause unexpected behavior. Microsoft cannot guarantee that you can solve problems that result from the incorrect use of this DBCC command. Use this DBCC command at your own risk. This DBCC command may not be available in future versions of SQL Server. For a list of the supported DBCC commands, see the "DBCC" topic in the Transact-SQL Reference section of SQL Server Books Online.
Using the DBCC STACKDUMP or CTRL+C+D operation to dump all stack traces in the SQL Server error log on a Windows 95 and Windows 98 install causes a fatal exception of the SQL Server process.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 239773 - Last Review: October 21, 2013 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB239773

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com