FIX: A trace file may be reported as corrupted and contains a 128 KB region of zeros in SQL Server 2000 (328616)

The information in this article applies to:

Microsoft SQL Server 2000 Developer Edition
Microsoft SQL Server 2000 Standard Edition
Microsoft SQL Server 2000 Enterprise Edition
Microsoft SQL Server 2000 Personal Edition
Microsoft SQL Server 2000 Enterprise Evaluation Edition
Microsoft SQL Server 2000 Workgroup Edition
Microsoft SQL Server 2000 Desktop Engine (MSDE)
Microsoft SQL Server 2000 Developer Edition 64 bit
Microsoft SQL Server 2000 Enterprise Edition 64-bit

This article was previously published under Q328616

Bug #: 360280 (SHILOH_BUGS)

SYMPTOMS

In Microsoft SQL Server 2000, when you open a server-generated trace file in SQL Profiler or when you read the trace file by using the fn_trace_gettable function, the trace file may be reported as corrupted. If you examine the file by using a hexadecimal editor, the section that was read when the error was raised may contain a 128 KB region of zeros.

CAUSE

This problem occurs because a race condition exists in the code. This race condition computes the asynchronous write logic and the offset in the file at which a particular set of data is written.

This behavior can cause a block to be written at an offset. This offset is 128 KB after the location at which the block should be written. Therefore, a 128 KB region of zeros is left in the file.

RESOLUTION

To resolve this problem, obtain the latest service pack for SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:	Major	Last Reviewed:	8/4/2005
Keywords:	kbbug kbfix kbSQLServ2000sp3fix KB328616 kbAudDeveloper