Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: A failfast occurs in the just-in-time code when DestroyManagedStub method notifications are received in COM+ 1.5


View products that this article applies to.

Symptoms

In Microsoft COM+ 1.5, a failfast occurs in the just-in-time (JIT) code when DestroyManagedStub method notifications are received from the ServicedComponentProxy class.

↑ Back to the top


Cause

This problem occurs because a race condition occurs after a stub is destroyed and before another thread tries to enter the context.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix rollup package information

This problem is fixed in the Microsoft Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6. For more information about the hotfix rollup package that contains this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
897667 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6

Hotfix information

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix rollup package. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to more support questions and issues that do not qualify for the specific update in question.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


Keywords: kbwinserv2003sp2fix, kbwinserv2003presp1fix, kbqfe, kbfix, kbbug, KB899597

↑ Back to the top

Article Info
Article ID : 899597
Revision : 3
Created on : 9/28/2011
Published on : 9/28/2011
Exists online : False
Views : 340