Article ID: 911678 - Last Review: November 2, 2007 - Revision: 1.6 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
Bug #: 474780 (SQL Server 8.0) On This PageSUMMARYThis
article describes the following about this hotfix release:
SYMPTOMSWhen 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
'Drive:\Path\FileName_YYYYMMDDHHMMSS.trc'
. 290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the most recent SQL
Server 2000 service pack
CAUSEThis problem
may occur because you try to load a trace file that is
damaged. RESOLUTIONThe installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesYou must have SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.Restart informationYou do not have to restart the computer after you apply this hotfix.Hotfix file informationThis 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, 32-bit versionsCollapse this table
SQL Server 2000, Itanium architecture versionCollapse this table
WORKAROUNDTo work around this
problem you may use the SQL Profiler to manually open the trace file and export
the file to a table. STATUSMicrosoft has confirmed that this is a
bug in the Microsoft products that are listed in the "Applies to"
section. MORE INFORMATIONNotes
822499
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/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) APPLIES TO
| Article Translations
|
Back to the top
