FIX: The "Audit Logout" event does not appear in the trace results file when you run a profiler trace against a linked server instance in SQL Server 2000 (917593)


The information in this article 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

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:

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

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 nameFile versionFile sizeDateTimePlatformSP requirement
Autoplt.dll2000.80.1035.0664,12825-Apr-200608:09x86SP3
Console.exe2000.80.1035.078,40025-Apr-200608:09x86SP3
Ctasksui.dll2000.80.1035.0332,35225-Apr-200608:09x86SP3
Custtask.dll2000.80.1035.0315,96825-Apr-200608:09x86SP3
Dbmslpcn.dll2000.80.1035.033,34025-Apr-200608:09x86SP3
Dtspkg.dll2000.80.1035.01,905,21625-Apr-200608:09x86SP3
Dtspump.dll2000.80.1035.0528,96025-Apr-200608:09x86SP3
Dtsui.dll2000.80.1035.01,557,05225-Apr-200608:09x86SP3
Dtswiz.dll2000.80.1035.0639,55225-Apr-200608:09x86SP3
Impprov.dll2000.80.1035.0102,99225-Apr-200608:09x86SP3
Isqlw.exe2000.80.1035.0352,82825-Apr-200608:09x86SP3
Itwiz.exe2000.80.1035.082,49225-Apr-200608:09x86SP3
Msgprox.dll2000.80.1035.090,69225-Apr-200608:09x86SP3
Mssdi98.dll8.11.41022.0226,30415-Apr-200500:59x86SP3
Odsole70.dll2000.80.1035.062,02425-Apr-200608:09x86SP3
Opends60.dll2000.80.1035.025,14425-Apr-200608:09x86SP3
Osql.exe2000.80.1035.057,90425-Apr-200608:09x86SP3
Pfutil80.dll2000.80.1035.0279,10425-Apr-200608:09x86SP3
Qrdrsvc.exe2000.80.1035.0143,94025-Apr-200608:09x86SP3
Replprov.dll2000.80.1035.0221,76825-Apr-200608:09x86SP3
Replrec.dll2000.80.1035.0307,78425-Apr-200608:09x86SP3
Rinitcom.dll2000.80.1035.0287,30425-Apr-200608:09x86SP3
Sdiclnt.dll2000.80.1035.078,41625-Apr-200608:09x86SP3
Semexec.dll2000.80.1035.0823,87225-Apr-200608:09x86SP3
Semmap.dll2000.80.1035.066,11225-Apr-200608:09x86SP3
Semnt.dll2000.80.1035.057,91625-Apr-200608:09x86SP3
Semobj.dll2000.80.1035.0492,09625-Apr-200608:09x86SP3
Snapshot.exe2000.80.1035.053,83225-Apr-200608:09x86SP3
Sqlagent.dll2000.80.1035.028,67225-Apr-200608:08x86SP3
Sqlagent.exe2000.80.1035.0311,87225-Apr-200608:09x86SP3
Sqlakw32.dll2000.80.1035.0168,00125-Apr-200608:08x86SP3
Sqlctr80.dll2000.80.1035.033,34425-Apr-200608:09x86SP3
Sqldiag.exe2000.80.1035.090,11225-Apr-200607:24x86SP3
Sqldmo.dll2000.80.1035.04,215,36025-Apr-200608:09x86SP3
Sqlmaint.exe2000.80.1035.0156,22425-Apr-200608:09x86SP3
Sqlmap70.dll2000.80.1035.0180,79225-Apr-200608:09x86SP3
Sqlmmc.dll2000.80.1035.0188,99225-Apr-200608:09x86SP3
Sqlqry.dll2000.80.1035.0401,98425-Apr-200608:09x86SP3
Sqlrepss.dll2000.80.1035.057,92025-Apr-200608:09x86SP3
Sqlservr.exe2000.80.1035.07,725,13725-Apr-200608:09x86SP3
Sqlsort.dll2000.80.1035.0590,39625-Apr-200608:09x86SP3
Sqlvdi.dll2000.80.1035.045,64425-Apr-200608:09x86SP3
Sqsrvres.dll2000.80.1035.0106,58825-Apr-200608:09x86SP3
Ssmsgnet.dll2000.80.1035.033,34025-Apr-200608:09x86SP3
Ssmslpcn.dll2000.80.1035.033,34025-Apr-200608:09x86SP3
Ssmsqlgc.dll2000.80.1035.033,34025-Apr-200608:09x86SP3
Ssnetlib.dll2000.80.1035.082,49225-Apr-200608:09x86SP3
Ssnmpn70.dll2000.80.1035.025,14825-Apr-200608:09x86SP3
Stardds.dll2000.80.1035.0123,45625-Apr-200608:09x86SP3
Svrnetcn.dll2000.80.1035.0158,26825-Apr-200608:09x86SP3
Svrnetcn.exe2000.80.1035.076,41625-Apr-200608:09x86SP3
Ums.dll2000.80.1035.049,22825-Apr-200608:09x86SP3
Xplog70.dll2000.80.1035.074,30425-Apr-200608:09x86SP3
Xpweb70.dll2000.80.1035.098,87225-Apr-200608:09x86SP3
SQL Server 2000 SP4 32-bit
File nameFile versionFile sizeDateTimePlatformSP requirement
Dtsui.dll2000.80.2192.01,593,34404-Apr-200606:00x86SP4
Impprov.dll2000.80.2192.0102,40004-Apr-200606:00x86SP4
Msgprox.dll2000.80.2192.094,20804-Apr-200606:00x86SP4
Msrpjt40.dll4.10.9424.0188,47324-Jan-200608:13x86SP4
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86SP4
Ntwdblib.dll2000.80.2192.0290,81604-Apr-200606:00x86SP4
Odsole70.dll2000.80.2192.069,63204-Apr-200606:00x86SP4
Osql.exe2000.80.2192.057,34404-Apr-200602:28x86SP4
Pfclnt80.dll2000.80.2192.0430,08004-Apr-200606:00x86SP4
Replmerg.exe2000.80.2192.0163,84004-Apr-200602:49x86SP4
Replprov.dll2000.80.2192.0237,56804-Apr-200606:00x86SP4
Replrec.dll2000.80.2192.0315,39204-Apr-200606:00x86SP4
Replsub.dll2000.80.2192.0270,33604-Apr-200606:00x86SP4
Semexec.dll2000.80.2192.0856,06404-Apr-200606:00x86SP4
Sqlagent.exe2000.80.2192.0323,58404-Apr-200601:48x86SP4
Sqldiag.exe2000.80.2192.0118,78404-Apr-200604:33x86SP4
Sqldmo.dll2000.80.2192.04,362,24004-Apr-200606:00x86SP4
Sqlfth75.dll2000.80.2192.0102,40004-Apr-200602:22x86SP4
Sqlservr.exe2000.80.2192.09,162,75204-Apr-200605:59x86SP4
Sqlsort.dll2000.80.2192.0589,82404-Apr-200606:00x86SP4
Stardds.dll2000.80.2192.0176,12804-Apr-200606:00x86SP4
Svrnetcn.dll2000.80.2192.0110,59204-Apr-200606:00x86SP4
Ums.dll2000.80.2192.035,32804-Apr-200606:00x86SP4
Xpstar.dll2000.80.2192.0311,29604-Apr-200606:00x86SP4
SQL Server 2000 SP4 64-bit
File nameFile versionFile sizeDateTimePlatformSP requirement
Impprov.dll2000.80.2192.0244,73606-Apr-200611:16Not ApplicableSP4
Msgprox.dll2000.80.2192.0188,41606-Apr-200611:16Not ApplicableSP4
Mssdi98.dll8.11.50523.0758,78406-Apr-200611:16Not ApplicableSP4
Msvcr71.dll7.10.3052.4348,16006-Apr-200611:16Not ApplicableSP4
Odsole70.dll2000.80.2192.0150,52806-Apr-200611:16Not ApplicableSP4
Osql.exe2000.80.2192.0149,50406-Apr-200611:16Not ApplicableSP4
Pfclnt80.dll2000.80.2192.01,187,84006-Apr-200611:16Not ApplicableSP4
Pfclnt80.dll2000.80.2192.0430,08006-Apr-200611:16Not ApplicableSP4
Replmerg.exe2000.80.2192.0375,29606-Apr-200611:16Not ApplicableSP4
Replprov.dll2000.80.2192.0538,62406-Apr-200611:16Not ApplicableSP4
Replprov2.dll2000.80.2192.0538,62406-Apr-200611:16Not ApplicableSP4
Replrec.dll2000.80.2192.0775,16806-Apr-200611:16Not ApplicableSP4
Replrec2.dll2000.80.2192.0775,16806-Apr-200611:16Not ApplicableSP4
Replsub.dll2000.80.2192.0641,02406-Apr-200611:16Not ApplicableSP4
Sqlagent.exe2000.80.2192.01,061,37606-Apr-200611:16Not ApplicableSP4
Sqldiag.exe2000.80.2192.0334,33606-Apr-200611:16Not ApplicableSP4
Sqldmo.dll2000.80.2192.04,362,24006-Apr-200611:16Not ApplicableSP4
Sqldmo.dll2000.80.2192.013,860,35206-Apr-200611:16Not ApplicableSP4
Sqlevn70.rll2000.80.2192.035,32806-Apr-200611:16Not ApplicableSP4
Sqlfth75.dll2000.80.2192.0246,78406-Apr-200611:16Not ApplicableSP4
Sqlservr.exe2000.80.2192.024,932,86406-Apr-200611:16Not ApplicableSP4
Sqlsort.dll2000.80.2192.0617,47206-Apr-200611:16Not ApplicableSP4
Sqlsort.dll2000.80.2192.0617,47206-Apr-200611:16Not ApplicableSP4
Sqlsort.dll2000.80.2192.0617,47206-Apr-200611:16Not ApplicableSP4
Svrnetcn.dll2000.80.2192.0427,52006-Apr-200611:16Not ApplicableSP4
Xpstar.dll2000.80.2192.0873,47206-Apr-200611:16Not ApplicableSP4

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:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmdac/html/pooling2.asp

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

Modification Type:MinorLast Reviewed:9/22/2006
Keywords:kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB917593 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.