COM+ Access Violation When You Create New Activity Under Low Memory Situation (304214)

The information in this article applies to:

Microsoft COM+ 1.0, when used with:
- the operating system: Microsoft Windows 2000

This article was previously published under Q304214

SYMPTOMS

In a low memory situation, you may receive an access violation in COM+ with following call stack:

1d41f2d4 6956caf3 COMSVCS!Map<_GUID,IUnknown*,HashGUID,EmptyMapBase>__grow+0x66 
1d41f2fc 695371ed COMSVCS!CSafeGuidToInterfaceMap__Add+0xf3 
1d41f310 69570adb COMSVCS!CActivity__Create+0x7d 
1d41f330 6956d510 COMSVCS!AptReference__AptReference+0x5b 
1d41f33c 6956d483 COMSVCS!CAsyncCall__CAsyncCall+0x70 
1d41f344 6956dac2 COMSVCS!CAsyncCall__Create+0x43 
1d41f350 74a2c3e1 COMSVCS!MTSCreateActivity+0x22 
0002bf20 00000000 asp!VariantResolveDispatch+0x7e

CAUSE

This problem occurs because a memory pointer that is returned from memory allocation is not checked against NULL in the internal map code of COM+.

RESOLUTION

To resolve this problem, obtain Microsoft COM+ Hotfix Rollup 15. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

306417 INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 15

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 3.

Modification Type:	Major	Last Reviewed:	6/5/2003
Keywords:	kbbug kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB304214