FIX: SQL Profiler Generates Error when Reading Trace Files that Exceed 1023 SPIDs (272737)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q272737 BUG #: 235343 (SHILOH_BUGS)
BUG #: 353327
(SHILOH_BUGS)
BUG #: 353226 (SHILOH_BUGS) 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.
RESOLUTIONTo 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
WORKAROUND Stop the trace before the threshold of 1023 connections is
reached. STATUSMicrosoft has confirmed that this is a
problem in SQL Server 2000.
This problem was first corrected in SQL Server 2000
Service Pack 1.
| Modification Type: | Major | Last Reviewed: | 10/17/2003 |
|---|
| Keywords: | kbBug kbfix kbSQLServ2000sp1fix KB272737 |
|---|
|