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 (911678)
The information in this article 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 64 bit
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 474780 (SQL Server 8.0)
SUMMARYThis
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.
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'
. For a list of previous hotfixes, see the "Microsoft SQL
Server 2000 Service Pack 4" section in the following Microsoft Knowledge Base
article:
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.RESOLUTIONHotfix informationA 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: 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. 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 versions |
Dtsui.dll | 2000.80.2175.0 | 1,593,344 | 02-Dec-2005 | 08:54 | x86 | Impprov.dll | 2000.80.2175.0 | 102,400 | 02-Dec-2005 | 08:54 | x86 | Mssdi98.dll | 8.11.50523.0 | 239,104 | 06-Jun-2005 | 22:46 | x86 | Ntwdblib.dll | 2000.80.2175.0 | 290,816 | 02-Dec-2005 | 08:54 | x86 | Odsole70.dll | 2000.80.2175.0 | 69,632 | 02-Dec-2005 | 08:54 | x86 | Osql.exe | 2000.80.2039.0 | 57,344 | 02-Dec-2005 | 10:51 | x86 | Pfclnt80.dll | 2000.80.2175.0 | 430,080 | 02-Dec-2005 | 08:54 | x86 | Procsyst.sql | Not
Applicable | 552,068 | 17-Jun-2005 | 00:15 | Not
Applicable | Replprov.dll | 2000.80.2175.0 | 237,568 | 02-Dec-2005 | 08:54 | x86 | Semexec.dll | 2000.80.2175.0 | 856,064 | 02-Dec-2005 | 08:54 | x86 | Sp4_serv_qfe.sql | Not
Applicable | 18,810 | 17-Jun-2005 | 00:15 | Not
Applicable | Sqlagent.exe | 2000.80.2175.0 | 323,584 | 01-Dec-2005 | 20:04 | x86 | Sqldiag.exe | 2000.80.2175.0 | 118,784 | 01-Dec-2005 | 20:42 | x86 | Sqldmo.dll | 2000.80.2175.0 | 4,362,240 | 02-Dec-2005 | 08:54 | x86 | Sqlevn70.rll | 2000.80.2175.0 | 45,056 | 02-Dec-2005 | 08:54 | Not
Applicable | Sqlfth75.dll | 2000.80.2175.0 | 102,400 | 01-Dec-2005 | 20:11 | x86 | Sqlservr.exe | 2000.80.2175.0 | 9,162,752 | 02-Dec-2005 | 08:53 | x86 | Sqlsort.dll | 2000.80.2175.0 | 589,824 | 02-Dec-2005 | 08:54 | x86 | Stardds.dll | 2000.80.2175.0 | 176,128 | 02-Dec-2005 | 08:54 | x86 | Svrnetcn.dll | 2000.80.2175.0 | 110,592 | 02-Dec-2005 | 08:54 | x86 | Ums.dll | 2000.80.2175.0 | 35,328 | 02-Dec-2005 | 08:54 | x86 |
SQL Server 2000, Itanium architecture version |
Impprov.dll | 2000.80.2175.0 | 244,736 | 02-Dec-2005 | 08:56 | IA-64 | Mssdi98.dll | 8.11.50523.0 | 758,784 | 06-Jun-2005 | 22:46 | IA-64 | Odsole70.dll | 2000.80.2175.0 | 150,528 | 02-Dec-2005 | 08:55 | IA-64 | Pfclnt80.dll | 2000.80.2175.0 | 1,187,840 | 02-Dec-2005 | 09:11 | IA-64 | Replprov.dll | 2000.80.2175.0 | 538,624 | 02-Dec-2005 | 09:01 | IA-64 | Sqlagent.exe | 2000.80.2175.0 | 1,061,376 | 02-Dec-2005 | 09:11 | IA-64 | Sqldiag.exe | 2000.80.2175.0 | 334,336 | 02-Dec-2005 | 09:12 | IA-64 | Sqldmo.dll | 2000.80.2175.0 | 13,860,352 | 02-Dec-2005 | 09:16 | IA-64 | Sqlfth75.dll | 2000.80.2175.0 | 246,784 | 02-Dec-2005 | 08:56 | IA-64 | Sqlservr.exe | 2000.80.2175.0 | 24,930,816 | 02-Dec-2005 | 13:00 | IA-64 | Sqlsort.dll | 2000.80.2175.0 | 617,472 | 01-Dec-2005 | 20:03 | IA-64 | Svrnetcn.dll | 2000.80.2175.0 | 427,520 | 02-Dec-2005 | 09:08 | IA-64 | Sqlevn70.rll | 2000.80.2175.0 | 35,328 | 02-Dec-2005 | 13:01 | Not
Applicable | Note Because of file dependencies, the most recent hotfix that
contains these files may also contain additional files. 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.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbbug kbfix kbHotfixServer kbQFE kbpubtypekc KB911678 kbAudITPRO kbAudDeveloper |
---|
|