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

Article ID: 272737 - View products that this article applies to.
This article was previously published under Q272737
BUG #: 235343 (SHILOH_BUGS)
BUG #: 353327 (SHILOH_BUGS)
BUG #: 353226 (SHILOH_BUGS)
Expand all | Collapse all

SYMPTOMS

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.
Back to the top | Give Feedback

RESOLUTION

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
(http://support.microsoft.com/kb/290211/EN-US/ )
INF: How to Obtain the Latest SQL Server 2000 Service Pack
Back to the top | Give Feedback

WORKAROUND

Stop the trace before the threshold of 1023 connections is reached.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
Back to the top | Give Feedback

Properties

Article ID: 272737 - Last Review: October 17, 2003 - Revision: 4.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbbug kbfix kbsqlserv2000sp1fix KB272737
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top