Availability of Windows Server 2003 COM+ 1.5 Rollup Package 3 (883955)

SUMMARY

Issues that are fixed in the hotfix package

• 890634 DTC Clustered resource will not come online if Administrator account lacks SE_SECURITY_NAME privilege

• 875498 If the DTC service is restarted many times, the service eventually does not restart in Windows Server 2003

• An "8000ffff" error is returned by COM+ method calls
  
  An "8000ffff" error occurs when a CreateObject call is made in Visual Basic for Scripting (VBS) while you are running with a Windows-based script host (WScript.exe). The CreateObject method calls into the CoGetClassObject function. The function returns an incorrect result code that the script reports as "8000ffff".
  
• The Imoniker::GetDisplayName method does not obtain the correct display name in Japanese Windows Server 2003
  
  When Japanese characters are used for the Item name in the system standard Item moniker, the Japanese Item name will have unreadable characters when the name is saved and retrieved back.
  
  File moniker support has been changed to return the correct data for non-ANSI characters.
  
• DTC Proxy stops responding when xa_recover operations are initiated on separate threads
  
  One or more xa_recover operations that are initiated on separate threads may cause the Distributed Transaction Coordinator (DTC) proxy to stop responding.
  
  This hotfix includes new code that serializes the xa_recover operation to avoid a race condition that may occur when more than one resource manager thread calls the xa_recover function.
  
• COM+ Explorer does not update the statistics on instances of poolable objects in a library application
  
  Pooled component statistics do not update in the Component Services Explorer for instances of pooled objects.
  
  Object pool tracking has been changed to start tracking statistics for library applications.
  
• An SC_SCREENSAVE event or an SC_MONITORPOWER event causes continuous beeping
  
  The computer beeps continuously if an SC_SCREENSAVE event or an SC_MONITORPOWER event occurs during a pending COM call.
  
  COM+ has been changed to no longer sound the beep when a screen saver or power monitoring event occurs.
  
• Huge ComplustraceX.log files are created when the COM+ event system is used
  
  The COM+ event system creates any number of trace logs but cleans up only the first ten logs.
  
  The COM+ event system has been changed to automatically remove all trace logs. Typically, the COM+ event system keeps the last ten log files. If you want to increase or decrease the number of log files that are kept, you must modify the following registry subkey:
  
  HKLM\SOFTWARE\Microsoft\OLE\Instrumentation
  TraceLogFilesLimit (REG_DWORD)
• A RPC_C_AUTH_LEVEL_DEFAULT flag that is used at activation time or at later times can cause a "0x8001011a" error
  
  When you make a DCOM call, and you use the RPC_C_AUTH_LEVEL_DEFAULT activation time or a later time to set the RPC Authentication Level flag, the client may receive a "0x8001011a (RPC_E_NO_GOOD_SECURITY_PACKAGES)" error message.
  
  COM activation now remaps the RPC_C_AUTHN_DEFAULT flag to the RPC_C_AUTHN_GSS_NEGOTIATE constant to correct this error.
  
• Heap corruption occurs in the COM+ event system
  
  Heap corruption may occur in the COM+ event system. An access violation may result while event notification messages are processed if a call to the PostThreadMessage function does not succeed.
  
  The event system has been changed to correctly handle this scenario.
• The ole32!CoGetObjectContext function is slow in Webdata scenarios when it runs under common language runtime 2.0
  
  The ole32!CoGetObjectContext function is too slow in Webdata scenarios when the function runs under common language runtime 2.0.
  
  The CoGetObjectContext function has been changed to improve its efficiency.
  
• DTC proxy causes a memory leak in a client process when it calls the xa_start function
  
  The DTC proxy code can leak an internal object instance when the xa_start function is called by using an invalid XID.
  
• "A new COM+ tracing session is taking too much to open" error is logged
  
  If an event logging session takes more time than expected to open, the following error message may be logged in the event log:
  A new COM+ tracing session is taking too much to open
  This fix removes this message from the COM+ event system.
  
• The xa_rollback function call is not always sent when you perform a rollback
  
  The xa_rollback function call is not always sent when you perform a rollback with an Oracle-linked server from Microsoft SQL Server. This problem occurs when the Oracle-provided ologo function is called while the transaction is in the active state. The state transitions to TRANSTATE_UNILATERALLY_ABORTING without calling the xa_rollback function.
  
  This hotfix includes new code to allow DTC to call the xa_rollback function before entering TRANSTATE_UNILATERALLY_ABORTING.
  
• The ExportApplication method fails with ERROR_MORE_DATA if the RemoteServerName is longer than 16 characters
  
  If an Application Proxy RemoteServerName contains more than 16 characters in the Options tab of My Computer properties in Component Services, an attempt to export the Application Proxy will fail with ERROR_MORE_DATA.
  
  COM+ now supports RemoteServerName names of up to MAX_PATH in length.
  
• A memory leak occurs when you are using proxy and stub buffer objects
  
  Under some circumstances, COM may not release an internal object that is used to manage proxy and stub buffer objects.
  
  COM code has been changed to correctly release these objects.
  
• A memory leak occurs when you call the xa_open function in a client process while DTC is offline
  
  When you call the xa_open function in a client process while DTC is offline, a memory leak may occur.
  
  This hotfix includes new code that does not let an internal DTC object leak when a connection to Transaction Manager is unavailable, and an xa_open function call is in progress.
  
• A memory leak occurs when the CoUninitialize function is called in a loop
  
  When the CoUninitialize function is called in a loop, it may not clean up an internal synchronization object. For example, the problem may occur if you use the following procedure in code:
  1. CoInitialize(STA or MTA)
  2. for (x = 1 to 3) { CoCreateInstance(some object); someobject->Release(); }
  3. CoUninitialize
  4. Goto #1
  CoUnitialize code has been changed to correctly release these objects.
  
• "Overlapped I/O is in progress" message occurs when you try to log on user_domain\user for an application
  
  This error message is erroneous when the LsaLogonUser function fails after it is called from within a DCOM application.
  
  The message has been removed.
  
• A registry option to disable Nagle algorithm is available
  
  Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  
  This hotfix adds a new registry option that lets you control whether the Nagle algorithm socket option is set or not. To configure this option, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

     HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC\

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type TcpNoDelay for the name of the DWORD, and then press ENTER.
  5. Right-click TcpNoDelay, and then click Modify.
  6. In the Value data box, type 1 to turn on the Nagle algorithm socket option, or type 0 to turn off the option.
  7. Click OK, and then quit Registry Editor.