Availability of Windows XP COM+ Hotfix Rollup Package 13 (912817)

SUMMARY

Issues that are fixed in this hotfix package

• An event message is logged when Microsoft Internet Information Services (IIS) intrinsics are not correctly marshaled.
• A code defect causes a null pointer to be incorrectly referenced. This issue occurs under heavy load conditions.
• Code defects in data unmarshaling paths may cause a failfast condition and memory leak issues.
• The Microsoft Distributed Transaction Coordinator (MSDTC) does not start on an AMD64-based computer.
• The GetAuthenticationLevel function is added to the ITransactionBridgeNetworkConfig interface.
• SAFEARRAY structures that contain a User Defined Datatype are not correctly marshaled.
• The Ole32.dll file incorrectly returns a success code when you do not successfully read proxy-stub CLSID information from the registry.
• Security is improved because of changes in the proxy-creation code in the Ole32.dll file.
• Security is improved because of changes to Microsoft Component Object Model (COM) infrastructure interfaces. These interfaces can no longer be called from a remote client computer.
• DCOM processes that require a user name and a password do not work as expected when the local security identifier (SID) and logon SID for a user are required.
  
  Note This issue does not occur on a computer that is running Microsoft Windows XP Service Pack 2 (SP2).
• When you use the SaveChanges method to add a new transient subscription to the TransientSubscription collection, you may receive an "Access is denied" error message. This error message has an error code of 80070005.
• A subordinate may be removed from the subordinate list in the Transaction Manager because of a duplicate export error. When this behavior occurs, the MSDTC does not correctly decrement the total log record space that is currently being used.
• Concurrent garbage collection is disabled if the detected transaction bridge is managed after you apply this hotfix.
• You can query the MSDTC for security and network configuration information after you apply this hotfix. This information may include cluster resource information.
• You can query the MSDTC for the information that is required to correctly support cluster and remote proxy scenarios when you use the WS-AtomicTransaction protocol after you install this hotfix.
• Applications that use Microsoft Windows Installer may not install as expected. This issue occurs if a remote procedure call is made to Windows Installer to verify that a folder exists. If the folder exists and the Network Service account does not have Read permissions on the folder, the application may not install correctly. This issue can also cause slow performance because lots of events are written to the Application log in Event Viewer.