After Upgrade to SNA Server 4.0 SP2, COMTI Application Fails With "Out of Memory" Indication

ID: Q228495

The information in this article applies to:

SYMPTOMS

Upon invocation of a method of a COMTI component library, an "Out of memory" message is returned to the client application, and Microsoft Transaction Server writes event 4104 to the application event log. The following are examples of such event log entries.

The first two examples contain "eyecatchers": "KERNEL32!Interlocked..." and "(Exception: C0000005)." However, these are not necessarily present, as in the third example below.

Example 1.

Event ID: 4104
Source: Transaction Server
Type: Error Category:
Context Wrapper

An object call caused an exception. (Package: BroncBuster)
(ProgId: Library.Interface.1) (CLSID:
{014A26B5-C2A4-11D2-81C2-0001FA37721E}) (Interface: IDispatch)
(IID: {00020400-0000-0000-C000-000000000046}) (Method: 6)
(Microsoft Transaction Server Internals Information: File:
d:\viper\src\runtime\cw\cwlib.cpp, Line: 935) (Exception: C0000005)
(Address: 0x77f051a9)
KERNEL32!InterlockedExchangeAdd + 0x9
tagen!Ordinal95 + 0x5477 tagen!Ordinal95 + 0x216F
mtxex!DllUnregisterServer + 0xB393
mtxex!DllUnregisterServer + 0x102EC
In the above description, "Library.Interface.1" is the ProgID of the COMTI component library. Also, "Exception: C0000005" indicates an access violation.

Example 2.
Event ID: 4104
Source: Transaction Server
Type: Error Category:
Context Wrapper


An object call caused an exception. (Package: CedarBank) (ProgId:
Cedar.Bank.1) (CLSID: {EEB4EBF3-9A63-11D0-AB6F-00AA00C1479E}) (Interface:
IDispatch) (IID: {00020400-0000-0000-C000-000000000046}) (Method: 6)
(Microsoft Transaction Server Internals Information: File:
d:\viper\src\runtime\cw\cwlib.cpp, Line: 935) (Exception: C0000005)
(Address: 0x77f0515a)
KERNEL32!InterlockedIncrement + 0xA
mtxex!DllUnregisterServer + 0xB393
mtxex!DllUnregisterServer + 0x102EC
Example 3.
Event ID: 4104
Source: Transaction Server
Type: Error Category:
Context Wrapper


An object call caused an exception. (Package: TestVB)(ProgId:
TestPilote_COMTI.MCVB.1) (CLSID: {8D79A611-E784-11D2-9BD2-0008C7F7EC7C})
(Interface: _MCVB) (IID: {8D79A600-E784-11D2-9BD2-0008C7F7EC7C}) (Method:
6) (Microsoft Transaction Server Internals Information: File:
d:\viper\src\runtime\cw\cwlib.cpp, Line: 861)


CAUSE

COMTI runtime components try to manipulate Performance Monitor object counters in shared memory. The shared memory does not have appropriate access tokens, which leads to an access violation. The access violation is caught by Microsoft Transaction Server (MTS), which causes the "Out of memory" message to be presented. Simultaneously, MTS writes an event 4104 record to the Event Log.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

File name Date Time
Comtiperf.dll 02/24/99 05:25:26 AM
Tagen.dll 02/24/99 05:25:26 AM
Tranlu62.dll 02/24/99 05:25:26 AM

NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in COM Transaction Integrator for CICS and IMS, version 4.0 SP2.

Additional query words: 


Keywords          : 
Version           : WINDOWS:4.0 SP2,4.0SP2
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: July 28, 1999