Microsoft KB Archive/911678

= FIX: No rows may be returned, and you may receive an error message when you try to import SQL Profiler trace files into tables by using the fn_trace_gettable function in SQL Server 2000 =

Article ID: 911678

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



Bug #: 474780 (SQL Server 8.0)



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package.
 * The prerequisites for installing the hotfix package.
 * Information about whether you must restart the computer after you install the hotfix package.
 * Information about whether the hotfix package is replaced by any other hotfix package.
 * Information about whether you must make any registry changes.
 * The files that are contained in the hotfix package.



SYMPTOMS
When you capture a SQL Profiler trace in a file and then you try to import the trace files into tables by using the fn_trace_gettable function in Microsoft SQL Server 2000, no rows may be returned. Additionally, you may receive the following error message:

Server: Msg 568, Level 16, State 10, Line 1 Server encountered an error ' :\ '.

For a list of previous hotfixes, see the &quot;Microsoft SQL Server 2000 Service Pack 4&quot; section in the following Microsoft Knowledge Base article:

290211 How to obtain the most recent SQL Server 2000 service pack



CAUSE
This problem may occur because you try to load a trace file that is damaged.



RESOLUTION
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
 * The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

Note This issue does not occur on systems that use the Intel Itanium processor architecture.
 * The system is running a 64-bit version of the Microsoft Windows Server operating system.
 * The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
You must have SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

Restart information
You do not have to restart the computer after you apply this hotfix.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000, Itanium architecture version
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.



WORKAROUND
To work around this problem you may use the SQL Profiler to manually open the trace file and export the file to a table.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
Notes
 * To enable this hotfix, you must turn on a 1903 trace flag.
 * After you apply this hotfix, you can successfully import trace files into tables. However, you will continue to receive the error message.

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Stack information
* 009BA08C Module(sqlservr+005BA08C) (CStackDump::GetContextAndDump+0000002F Line 1973+00000002)
 * 009BA9B5 Module(sqlservr+005BA9B5) (stackTrace+0000029A Line 4366+00000013)
 * 006EE757 Module(sqlservr+002EE757) (ex_raise2+00000178 Line 1034+0000001F)
 * 005FA686 Module(sqlservr+001FA686) (ex_raise+00000063 Line 1209+00000014)
 * 007D568A Module(sqlservr+003D568A) (CRowsetTraceTable::FGetNextRow+000003CE Line 6233+00000015)
 * 00A92275 Module(sqlservr+00692275) (CUtRowset::GetNextRows+0000006F Line 1401+00000008)
 * 0060ECB0 Module(sqlservr+0020ECB0) (CQScanRmtScan::GetRow+000001F2 Line 1288+00000016)
 * 00869FDB Module(sqlservr+00469FDB) (CQScanProject::GetRow+0000001A Line 175+00000000)
 * 0040FF15 Module(sqlservr+0000FF15) (CQScanTop::GetRow+000000DA Line 292+FFDBA619)
 * 0044BAB0 Module(sqlservr+0004BAB0) (CQScanUpdate::GetRow+0000014C Line 622+0000000C)
 * 0040C369 Module(sqlservr+0000C369) (CQueryScan::GetRow+00000078 Line 4386+00000000)
 * 0040C2ED Module(sqlservr+0000C2ED) (CStmtQuery::ErsqExecuteQuery+0000068F Line 955+0000000D)
 * 004168CF Module(sqlservr+000168CF) (CStmtDML::XretExecuteNormal+00000391 Line 1970+00000014)
 * 00415D04 Module(sqlservr+00015D04) (CMsqlExecContext::ExecuteStmts+00000446 Line 1593+0000000B)
 * 00416214 Module(sqlservr+00016214) (CMsqlExecContext::Execute+00000255 Line 1239+0000000B)

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB911678

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.