Microsoft KB Archive/917593

From BetaArchive Wiki

Article ID: 917593

Article Last Modified on 11/2/2007



APPLIES TO

  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Standard Edition



Bug #: 642 (SQL Hotfix)
Bug #: 50000135 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

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
  • Whether you must restart the computer after you install the hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package


SYMPTOMS

When you run a profiler trace against a linked server instance in Microsoft SQL Server 2000, the Audit Logout event does not appear in the trace results file. This problem may occur in the following scenario:

  • You have one instance of SQL Server 2000 (Instance A).
  • Instance A has a linked server (Instance B), and Instance B is configured to point to a remote instance of SQL Server 2000.
  • When you run a profiler trace against Instance B, the Audit Login event appears in the trace results file when Instance A connects to Instance B.
  • When you run a profiler trace against Instance B, the Audit Logout event does not appear in the trace results file when Instance A disconnects from Instance B.

For a list of all publicly released SQL Server 2000 post-service pack hotfixes, see the following article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4


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 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.

Prerequisites

For more information about how to obtain SQL Server 2000 Service Pack 4, 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


Restart information

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

Registry information

You do not have to change the registry.

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 of 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 item in Control Panel.

SQL Server 2000 SP3 32-bit
File name File version File size Date Time Platform SP requirement
Autoplt.dll 2000.80.1035.0 664,128 25-Apr-2006 08:09 x86 SP3
Console.exe 2000.80.1035.0 78,400 25-Apr-2006 08:09 x86 SP3
Ctasksui.dll 2000.80.1035.0 332,352 25-Apr-2006 08:09 x86 SP3
Custtask.dll 2000.80.1035.0 315,968 25-Apr-2006 08:09 x86 SP3
Dbmslpcn.dll 2000.80.1035.0 33,340 25-Apr-2006 08:09 x86 SP3
Dtspkg.dll 2000.80.1035.0 1,905,216 25-Apr-2006 08:09 x86 SP3
Dtspump.dll 2000.80.1035.0 528,960 25-Apr-2006 08:09 x86 SP3
Dtsui.dll 2000.80.1035.0 1,557,052 25-Apr-2006 08:09 x86 SP3
Dtswiz.dll 2000.80.1035.0 639,552 25-Apr-2006 08:09 x86 SP3
Impprov.dll 2000.80.1035.0 102,992 25-Apr-2006 08:09 x86 SP3
Isqlw.exe 2000.80.1035.0 352,828 25-Apr-2006 08:09 x86 SP3
Itwiz.exe 2000.80.1035.0 82,492 25-Apr-2006 08:09 x86 SP3
Msgprox.dll 2000.80.1035.0 90,692 25-Apr-2006 08:09 x86 SP3
Mssdi98.dll 8.11.41022.0 226,304 15-Apr-2005 00:59 x86 SP3
Odsole70.dll 2000.80.1035.0 62,024 25-Apr-2006 08:09 x86 SP3
Opends60.dll 2000.80.1035.0 25,144 25-Apr-2006 08:09 x86 SP3
Osql.exe 2000.80.1035.0 57,904 25-Apr-2006 08:09 x86 SP3
Pfutil80.dll 2000.80.1035.0 279,104 25-Apr-2006 08:09 x86 SP3
Qrdrsvc.exe 2000.80.1035.0 143,940 25-Apr-2006 08:09 x86 SP3
Replprov.dll 2000.80.1035.0 221,768 25-Apr-2006 08:09 x86 SP3
Replrec.dll 2000.80.1035.0 307,784 25-Apr-2006 08:09 x86 SP3
Rinitcom.dll 2000.80.1035.0 287,304 25-Apr-2006 08:09 x86 SP3
Sdiclnt.dll 2000.80.1035.0 78,416 25-Apr-2006 08:09 x86 SP3
Semexec.dll 2000.80.1035.0 823,872 25-Apr-2006 08:09 x86 SP3
Semmap.dll 2000.80.1035.0 66,112 25-Apr-2006 08:09 x86 SP3
Semnt.dll 2000.80.1035.0 57,916 25-Apr-2006 08:09 x86 SP3
Semobj.dll 2000.80.1035.0 492,096 25-Apr-2006 08:09 x86 SP3
Snapshot.exe 2000.80.1035.0 53,832 25-Apr-2006 08:09 x86 SP3
Sqlagent.dll 2000.80.1035.0 28,672 25-Apr-2006 08:08 x86 SP3
Sqlagent.exe 2000.80.1035.0 311,872 25-Apr-2006 08:09 x86 SP3
Sqlakw32.dll 2000.80.1035.0 168,001 25-Apr-2006 08:08 x86 SP3
Sqlctr80.dll 2000.80.1035.0 33,344 25-Apr-2006 08:09 x86 SP3
Sqldiag.exe 2000.80.1035.0 90,112 25-Apr-2006 07:24 x86 SP3
Sqldmo.dll 2000.80.1035.0 4,215,360 25-Apr-2006 08:09 x86 SP3
Sqlmaint.exe 2000.80.1035.0 156,224 25-Apr-2006 08:09 x86 SP3
Sqlmap70.dll 2000.80.1035.0 180,792 25-Apr-2006 08:09 x86 SP3
Sqlmmc.dll 2000.80.1035.0 188,992 25-Apr-2006 08:09 x86 SP3
Sqlqry.dll 2000.80.1035.0 401,984 25-Apr-2006 08:09 x86 SP3
Sqlrepss.dll 2000.80.1035.0 57,920 25-Apr-2006 08:09 x86 SP3
Sqlservr.exe 2000.80.1035.0 7,725,137 25-Apr-2006 08:09 x86 SP3
Sqlsort.dll 2000.80.1035.0 590,396 25-Apr-2006 08:09 x86 SP3
Sqlvdi.dll 2000.80.1035.0 45,644 25-Apr-2006 08:09 x86 SP3
Sqsrvres.dll 2000.80.1035.0 106,588 25-Apr-2006 08:09 x86 SP3
Ssmsgnet.dll 2000.80.1035.0 33,340 25-Apr-2006 08:09 x86 SP3
Ssmslpcn.dll 2000.80.1035.0 33,340 25-Apr-2006 08:09 x86 SP3
Ssmsqlgc.dll 2000.80.1035.0 33,340 25-Apr-2006 08:09 x86 SP3
Ssnetlib.dll 2000.80.1035.0 82,492 25-Apr-2006 08:09 x86 SP3
Ssnmpn70.dll 2000.80.1035.0 25,148 25-Apr-2006 08:09 x86 SP3
Stardds.dll 2000.80.1035.0 123,456 25-Apr-2006 08:09 x86 SP3
Svrnetcn.dll 2000.80.1035.0 158,268 25-Apr-2006 08:09 x86 SP3
Svrnetcn.exe 2000.80.1035.0 76,416 25-Apr-2006 08:09 x86 SP3
Ums.dll 2000.80.1035.0 49,228 25-Apr-2006 08:09 x86 SP3
Xplog70.dll 2000.80.1035.0 74,304 25-Apr-2006 08:09 x86 SP3
Xpweb70.dll 2000.80.1035.0 98,872 25-Apr-2006 08:09 x86 SP3
SQL Server 2000 SP4 32-bit
File name File version File size Date Time Platform SP requirement
Dtsui.dll 2000.80.2192.0 1,593,344 04-Apr-2006 06:00 x86 SP4
Impprov.dll 2000.80.2192.0 102,400 04-Apr-2006 06:00 x86 SP4
Msgprox.dll 2000.80.2192.0 94,208 04-Apr-2006 06:00 x86 SP4
Msrpjt40.dll 4.10.9424.0 188,473 24-Jan-2006 08:13 x86 SP4
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 22:46 x86 SP4
Ntwdblib.dll 2000.80.2192.0 290,816 04-Apr-2006 06:00 x86 SP4
Odsole70.dll 2000.80.2192.0 69,632 04-Apr-2006 06:00 x86 SP4
Osql.exe 2000.80.2192.0 57,344 04-Apr-2006 02:28 x86 SP4
Pfclnt80.dll 2000.80.2192.0 430,080 04-Apr-2006 06:00 x86 SP4
Replmerg.exe 2000.80.2192.0 163,840 04-Apr-2006 02:49 x86 SP4
Replprov.dll 2000.80.2192.0 237,568 04-Apr-2006 06:00 x86 SP4
Replrec.dll 2000.80.2192.0 315,392 04-Apr-2006 06:00 x86 SP4
Replsub.dll 2000.80.2192.0 270,336 04-Apr-2006 06:00 x86 SP4
Semexec.dll 2000.80.2192.0 856,064 04-Apr-2006 06:00 x86 SP4
Sqlagent.exe 2000.80.2192.0 323,584 04-Apr-2006 01:48 x86 SP4
Sqldiag.exe 2000.80.2192.0 118,784 04-Apr-2006 04:33 x86 SP4
Sqldmo.dll 2000.80.2192.0 4,362,240 04-Apr-2006 06:00 x86 SP4
Sqlfth75.dll 2000.80.2192.0 102,400 04-Apr-2006 02:22 x86 SP4
Sqlservr.exe 2000.80.2192.0 9,162,752 04-Apr-2006 05:59 x86 SP4
Sqlsort.dll 2000.80.2192.0 589,824 04-Apr-2006 06:00 x86 SP4
Stardds.dll 2000.80.2192.0 176,128 04-Apr-2006 06:00 x86 SP4
Svrnetcn.dll 2000.80.2192.0 110,592 04-Apr-2006 06:00 x86 SP4
Ums.dll 2000.80.2192.0 35,328 04-Apr-2006 06:00 x86 SP4
Xpstar.dll 2000.80.2192.0 311,296 04-Apr-2006 06:00 x86 SP4
SQL Server 2000 SP4 64-bit
File name File version File size Date Time Platform SP requirement
Impprov.dll 2000.80.2192.0 244,736 06-Apr-2006 11:16 Not Applicable SP4
Msgprox.dll 2000.80.2192.0 188,416 06-Apr-2006 11:16 Not Applicable SP4
Mssdi98.dll 8.11.50523.0 758,784 06-Apr-2006 11:16 Not Applicable SP4
Msvcr71.dll 7.10.3052.4 348,160 06-Apr-2006 11:16 Not Applicable SP4
Odsole70.dll 2000.80.2192.0 150,528 06-Apr-2006 11:16 Not Applicable SP4
Osql.exe 2000.80.2192.0 149,504 06-Apr-2006 11:16 Not Applicable SP4
Pfclnt80.dll 2000.80.2192.0 1,187,840 06-Apr-2006 11:16 Not Applicable SP4
Pfclnt80.dll 2000.80.2192.0 430,080 06-Apr-2006 11:16 Not Applicable SP4
Replmerg.exe 2000.80.2192.0 375,296 06-Apr-2006 11:16 Not Applicable SP4
Replprov.dll 2000.80.2192.0 538,624 06-Apr-2006 11:16 Not Applicable SP4
Replprov2.dll 2000.80.2192.0 538,624 06-Apr-2006 11:16 Not Applicable SP4
Replrec.dll 2000.80.2192.0 775,168 06-Apr-2006 11:16 Not Applicable SP4
Replrec2.dll 2000.80.2192.0 775,168 06-Apr-2006 11:16 Not Applicable SP4
Replsub.dll 2000.80.2192.0 641,024 06-Apr-2006 11:16 Not Applicable SP4
Sqlagent.exe 2000.80.2192.0 1,061,376 06-Apr-2006 11:16 Not Applicable SP4
Sqldiag.exe 2000.80.2192.0 334,336 06-Apr-2006 11:16 Not Applicable SP4
Sqldmo.dll 2000.80.2192.0 4,362,240 06-Apr-2006 11:16 Not Applicable SP4
Sqldmo.dll 2000.80.2192.0 13,860,352 06-Apr-2006 11:16 Not Applicable SP4
Sqlevn70.rll 2000.80.2192.0 35,328 06-Apr-2006 11:16 Not Applicable SP4
Sqlfth75.dll 2000.80.2192.0 246,784 06-Apr-2006 11:16 Not Applicable SP4
Sqlservr.exe 2000.80.2192.0 24,932,864 06-Apr-2006 11:16 Not Applicable SP4
Sqlsort.dll 2000.80.2192.0 617,472 06-Apr-2006 11:16 Not Applicable SP4
Sqlsort.dll 2000.80.2192.0 617,472 06-Apr-2006 11:16 Not Applicable SP4
Sqlsort.dll 2000.80.2192.0 617,472 06-Apr-2006 11:16 Not Applicable SP4
Svrnetcn.dll 2000.80.2192.0 427,520 06-Apr-2006 11:16 Not Applicable SP4
Xpstar.dll 2000.80.2192.0 873,472 06-Apr-2006 11:16 Not Applicable SP4


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Linked server connections from SQL Server 2000 clients rely on connection pooling. After each batch is completed against the linked server, the client instance sends the sp_reset_connection suffix command to clean up the following connection metadata information:

  • The accumulated metadata in the sysprocesses columns.
  • The data columns for the trace event. The data columns can include the CPU time, the read operations, the write operations, the duration, the start time, and the end time.
  • Other information, such as error information, temp tables, and SET options.

After the sp_reset_connection stored procedure is performed, the SPID goes into Dormant status on the remote linked server instance. You can see the status of the SPID when you query the sysprocesses system table.

SELECT * FROM MASTER.DBO.SYSPROCESSES WHERE Status='Dormant'

If there are no additional queries to the same linked server, the client instance of SQL Server disconnects the dormant connection to the remote linked server instance after 5 minutes of inactivity. However, the Audit Logout event is not produced, even though the connection is disconnected successfully.

This problem does not affect typical applications that use SQLOLEDB resource pooling, ODBC connection pooling, or SQLClient pooling. Those forms of pooling issue the internal procedure call to the sp_reset_connection stored procedure as a prefix to each additional command that is executed. Therefore, connections that are idle are not reset until a new command comes in. This behavior differs from the linked server behavior, where the sp_reset_connection command is issued as a suffix to the last completed command, even if additional commands come later.

In linked server scenarios, the SPID that has a Dormant status is the one that will soon be disconnected after it is idle, and that SPID does not produce the Audit Logout trace event. In regular pooling scenarios, the SPID usually has a Sleeping status when it is idle. After several minutes of inactivity, depending on how pooling is configured, the connection is disconnected, and the Audit Logout trace event is produced.

REFERENCES

For more information about how to use SQL Profiler and SQL Trace, visit the following Microsoft Developer Network (MSDN) Web sites:

For more information about the benefits, the features, and the behavior of pooling in Microsoft Data Access Components (MDAC) architecture, visit the following MSDN Web site:

For more information, 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


Keywords: kbbug kbfix kbtshoot kbhotfixserver kbqfe kbpubtypekc KB917593