FIX: The ObjectControl_Activate method may not be called for a component that is written in Visual Basic when a client application tries to create a COM+ component (911194)


The information in this article applies to:

  • Microsoft COM+ 1.0
  • Microsoft COM+ 1.5
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
  • Microsoft Visual Basic Professional Edition for Windows, Versions 6.0

SYMPTOMS

When a client application tries to create a Microsoft COM+ component, the ObjectControl_Activate method may not be called for a component that is written in Visual Basic. Typically, you experience this problem when you use Microsoft Visual Basic Professional Edition for Windows 6.0 to debug a component that is hosted in COM+. When this problem occurs, an error message that is similar to the following may be logged in the event log:
Event Type: Error
Event Source: COM+
Event Category: (98)
Event ID: 4822
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: A condition has occurred that indicates this COM+ application is in an unstable state or is not functioning correctly.
Assertion Failure: !punkToActivate Server Application ID: GUID
Server Application Instance ID: GUID
Server Application Name: System Application
The serious nature of this error has caused the process to terminate.
COM+ Services Internals Information:
File: c:\xpsp2\com\com1x\src\comsvcs\jit\jit.cpp, Line: 556 Comsvcs.dll file version: ENU 2001.12.4414.305 shp
For more information, see Help and Support Center at http://support.microsoft.com.

CAUSE

This problem occurs because marshaling of the context for the new object fails. Marshaling fails because the allocated buffer size is too small. Retry logic is implemented in the COM+ code. However, the Visual Basic 6.0 debug activator fails when the first marshaling try fails.

RESOLUTION

Hotfix rollup package information

To resolve this problem, obtain the hotfix rollup package that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

910720 Availability of Windows XP COM+ Hotfix Rollup Package 12

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MajorLast Reviewed:9/22/2006
Keywords:kbQFE kbfix kbprb KB911194 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.