Microsoft KB Archive/888000

= Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 31 =

Article ID: 888000

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft COM+ 1.0, when used with:
 * Microsoft Windows 2000 Service Pack 4

-





ARTICLE CONTENTS

 * SUMMARY
 * Issues that are fixed in the hotfix rollup package
 * hotfix rollup package information
 * Prerequisites
 * Restart information
 * hotfix rollup package replacement information
 * Registry information
 * File information
 * REFERENCES



SUMMARY
This article lists the Microsoft COM+ bugs that are fixed in the Microsoft Windows 2000 Post-Service Pack 4 (SP4) COM+ 1.0 Hotfix Rollup Package 31. Each hotfix rollup package contains all the fixes that were released in the previous Windows 2000 COM+ 1.0 hotfix rollup packages.

back to the top

Issues that are fixed in the hotfix rollup package
The following issue is fixed in this hotfix rollup package:  

871169 You may not be able to use Windows Backup to restore the system state on a computer that is running Windows 2000 Server with SP3 or SP4



The following issues are also fixed in this hotfix rollup package but were not previously documented in a Microsoft Knowledge Base article:  COM+/DTC operations may take a long time to run during the commit-phase of a transaction. Servers that are running Microsoft Internet Information Server 5.0 may appear to stop responding after you install Microsoft Application Center 2000. DCOM servers may start to respond slowly and eventually become unusable as unreleased COM objects accumulate on the server. You may receive an 800401fb error message when you delete a transient subscription to an event class after the subscriber's process has been terminated. Or, you may receive this error message when you try to create a new instance of the subscription. A memory leak may occur in Ole32.dll when you use proxy or stub dynamic link libraries.</li> COM+ applications may stop responding periodically.</li> When you use Iissync to synchronize the metabase of clustered Web servers, you find entries that are similar to the following in the %Windir%\System32\Com\Replication\Comrepl.Log file:

An unexpected error occured exporting application 'MyProxyApp'. Error code was 80070057.

Note In this message, the word &quot;occured&quot; is a misspelling for the word &quot;occurred.&quot;</li> A DCOM application may return the value RPC_E_DISCONNECTED.</li>  When you use the COM+ Message Queuing (also known as MSMQ) Message Mover utility, you may see the following message in the System event Log: Event Type: Error

Event Source: COM+

Event ID: 4177

Event Description:

MoveMessageLoop

Process Name: MessageMoverTool.exe

Error Code = 0xc00e001f :

COM+ Services Internals Information:

File: .\messagemover.cpp, Line: 222. </li></ul>

back to the top

<div class="moreinformation_section">

hotfix rollup package information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

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

http://support.microsoft.com/default.aspx?scid=fh;[LN;CNTACTMS]

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.

back to the top

Prerequisites
You must have Microsoft Windows 2000 with Service Pack 4 (SP4) installed to apply this hotfix rollup package.

back to the top

Restart information
You must restart your computer after you apply this hotfix rollup package.

back to the top

hotfix rollup package replacement information
This hotfix rollup package is not replaced by any later hotfix.

Resolutions for problems that are fixed in the Windows 2000 COM+ 1.0 hotfix rollup packages are cumulative. The following is a list of Microsoft Knowledge Base articles for the previous hotfix rollup packages:  

840999 Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 30

</li></ul>

back to the top

Registry information
You do not have to create or modify any registry keys to enable any hotfixes that are contained in this hotfix rollup package.

back to the top

File information
This hotfix rollup package contains only those files that you must have to correct the issues that this article lists. This hotfix rollup package 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 rollup package 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. <pre class="fixed_text">  Date         Time   Version            Size    File name --  26-Oct-2004  13:58  2000.2.3516.0     169,232  Catsrv.dll 26-Oct-2004 13:58  2000.2.3516.0     595,728  Catsrvut.dll 26-Oct-2004 13:58  2000.2.3516.0      97,040  Clbcatex.dll 26-Oct-2004 13:58  2000.2.3516.0     553,744  Clbcatq.dll 26-Oct-2004 13:58  2000.2.3516.0      41,744  Colbact.dll 26-Oct-2004 13:58  2000.2.3516.0     198,416  Comadmin.dll 26-Oct-2004 13:58  2000.2.3516.0      97,552  Comrepl.dll 26-Oct-2004 13:58  2000.2.3421.351   342,288  Comsetup.dll 26-Oct-2004 13:58  2000.2.3516.0   1,471,248  Comsvcs.dll 26-Oct-2004 13:58  2000.2.3516.0     625,936  Comuid.dll 17-Oct-2004 05:40  2000.2.3516.0   1,812,968  Dtcsetup.exe 26-Oct-2004 13:58  2000.2.3516.0     240,400  Es.dll 26-Oct-2004 13:58  2000.2.3516.0      96,016  Msdtclog.dll 26-Oct-2004 14:58  2000.2.3516.0     718,096  Msdtcprx.dll 26-Oct-2004 13:58  2000.2.3516.0   1,140,496  Msdtctm.dll 26-Oct-2004 13:58  2000.2.3516.0     153,872  Msdtcui.dll 17-Oct-2004 06:05  2000.2.3516.0     155,408  Mtstocom.exe 26-Oct-2004 13:58  2000.2.3516.0      52,496  Mtxclu.dll 26-Oct-2004 13:58  2000.2.3516.0      26,896  Mtxdm.dll 26-Oct-2004 13:58  2000.2.3516.0      35,600  Mtxlegih.dll 26-Oct-2004 13:58  2000.2.3516.0     122,640  Mtxoci.dll 26-Oct-2004 13:58  5.0.2195.6990     955,664  Ole32.dll 11-Mar-2004 21:29  5.0.2195.6904     449,808  Rpcrt4.dll 26-Oct-2004 13:58  5.0.2195.6990     212,240  Rpcss.dll 12-Oct-2004 10:10  5.0.2195.6983   6,125,568  Sp3res.dll 26-Oct-2004 13:58  2000.2.3516.0      71,440  Stclient.dll 26-Oct-2004 13:58  2000.2.3516.0     398,608  Txfaux.dll 26-Oct-2004 13:58  2000.2.3516.0      18,704  Xolehlp.dll back to the top

This update adds the COMBND_SERVER_LOCALITY option for the IRpcOptions::Query Windows Management Instrumentation (WMI) method. WMI uses this option to determine whether a WMI connection is local or remote.

<div class="references_section">