Article ID: 899597 - Last Review: December 5, 2007 - Revision: 2.6 FIX: A failfast occurs in the just-in-time code when DestroyManagedStub method notifications are received in COM+ 1.5On This PageSYMPTOMSIn Microsoft COM+ 1.5, a failfast occurs in the just-in-time (JIT) code when DestroyManagedStub method notifications are received from the ServicedComponentProxy class. CAUSEThis problem occurs because a race condition occurs after a stub is destroyed and before another thread tries to enter the context. RESOLUTIONService pack informationTo 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
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003 Hotfix rollup package informationThis 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
(http://support.microsoft.com/kb/897667/
)
Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6
Hotfix informationTo 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:http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.
STATUSMicrosoft 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. APPLIES TO
| Article Translations
|
Back to the top
