Availability of Windows XP COM+ 1.5 Rollup Package 6 (828758)

INTRODUCTION

Issues that are fixed in this rollup package

• 319007 COM+ application stops responding on idle shutdown if you configure application as Queued and Listening

• Services Without Components (SWC) are not fully supported in Windows XP.
• The queued components (QC) Exception class does not appropriately handle messages that cannot be sent.
• A memory leak occurs when you use the ICrmLogControl::WriteLogRecordVariantsCRM Compensating Resource Manager (CRM) interface.
• The OnMethodCall event, the OnMethodReturn event, and the OnMethodException event are not generated for managed components.
• When you set up a new single-threaded apartment (STA) context, a deadlock may occur during the reuse of synchronization properties.
• When you create COM+ components and increase the initial pool size for the components, the additional components that you create are removed and cleaned up from the Microsoft .NET managed component pool after 5 minutes of inactivity. However, the unmanaged components remain.
• TCP sends data to the client after the disconnect is completed in a race condition.
• Conflicts between two modems are caused by the Impersonate user right.
• The CDllHost::DllGetClassObject function must verify parameters.
• You may not receive notification of the transaction outcome managed code.
• The DCOMCNFG utility does not return a valid authentication level value into the AppID registry subkey.
• When you cannot find the default authnsvc parameter for the OXIDEntry internal structure in the server's OXID binding, you pick the first authnsvc parameter from the server's bindings.
• A memory leak may occur when you create a COM+ 1.0 server application.
• When an access violation in the COM+ QC Dead Letter Queue Listener occurs, the IPlaybackControl::FinalClientRetry function may not be called.
• A Microsoft Distributed Transaction Coordinator (MSDTC) deadlock occurs in the UTSemReadWrite design.
• An access violation in the comsvcs!CNonRootTransactionStream::LeaveFillBuffer function occurs.
• An exception in the OLE32.DLL!CObjectContext::InternalRelease function causes Windows Error Reporting to report bucket 22606892.
• MSDTC shuts down after the timer object disappears.
• Microsoft Windows Installer Setup that is exported from Microsoft Windows XP fails on a computer that is running Microsoft Windows 2000.
• The Design Change Request (DCR) to enhance the ContextUtil named property extensions was implemented.
• The AccessCheck cache based remote procedure call (RPC) connections should deny or allow connections.
• Indoubt transactions do not immediately disappear from the list of indoubt transactions.
• When you use a dynamically loaded assembly to call the SetComplete method for a Microsoft .NET Enterprise Services component, the transaction may end.
• The Remote Procedure Call Server service (RPCSS) loops in the PingServer procedure because the ping may return 0x5.
• The EqualAuthInfo parameter is required to work well with the ANSI version of the COAUTHIDENTITY structure.
• The CheckLocalSecurity procedure may crash on a null context handle in the RPCSS.
• The ole32!CRemoteUnknown::DoCallback function is called from within the same process.
• When a race condition occurs, a multithreaded apartment (MTA) that is actually not shutting down becomes incorrectly marked as shutting down.
• When you use the global interface table (GIT) from different threads, a memory leak may occur.
• When a DCOM client has lost a callback connection, the object returns the RPC_E_DISCONNECTED value.
• When you install an application proxy that has a newer DLL version, the COMPLUS\{GUID} folder is not overwritten.
• The Mtxoci.dll file unloads before all threads are finished.
• When the COM+ catalog stores a user name as a string, the string may be in a different language on a Multilingual User Interface (MUI) system after you apply the hotfix that is described in the following Microsoft Knowledge Base article:

  281454 You cannot apply local security settings with MUI

• When one subscriber unregisters a subscription, a race condition causes valid subscribers to no longer receive all events.
• The AuthenticationCapability application property may reject some valid EOAC_ values.
• The CComCatalog::GetProcessInfoInternal function may not use the passed in flags as keys that cause the 32-bit surrogate activations to fail.
• When the COM+ event system detects a corrupted IEventSubscription object, many erroneous events are logged in the event log.
• A memory leak in the txfaux!TYPEINFOVTBL structure occurs.
• A MSDTC crash may cause queued component (QC) messages to become lost.
• A COM+ process may crash after you apply Windows 2000 Post-Service Pack 3 COM+ Hotfix Rollup 22.