FIX: SQL Profiler Generates Error when Reading Trace Files that Exceed 1023 SPIDs

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


SQL Server Profiler generates the following error message when you open a trace file that has more than 1023 connections (system process IDs [SPIDs]):
File may be corrupt or wrong data format.
This trace file cannot be opened by SQL Server Profiler.


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 the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


Stop the trace before the threshold of 1023 connections is reached.


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: 272737 - Last Review: January 16, 2015 - Revision: 4.2
  • Microsoft SQL Server 2000 Standard Edition
kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB272737

Contact us for more help

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