FIX: The call stack is missing frames when you debug a .NET Framework 2.0 application that uses COM interoperability

This article has been archived. It is offered "as is" and will no longer be updated.
When you debug a Microsoft .NET Framework 2.0 application that uses Microsoft Component Object Model (COM) interoperability, the native call stack is missing frames.

This problem occurs if the following conditions are true:
  • You make a call from native code into managed code.
  • The managed code is not in the default application domain.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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 additional support questions and issues that do not qualify for the specific update in question.


The following list contains prerequisites for the hotfix:
  • The Microsoft .NET Framework 2.0

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
x86-based computers
File nameFile versionFile sizeDate (UTC)Time (UTC)Platform
Normidna.nlpNot Applicable59,34203-Aug-200619:08Not Applicable
Normnfc.nlpNot Applicable45,79404-Aug-200604:03Not Applicable
Normnfd.nlpNot Applicable39,28403-Aug-200619:08Not Applicable
Normnfkc.nlpNot Applicable66,38403-Aug-200619:08Not Applicable
Normnfkd.nlpNot Applicable60,29403-Aug-200619:08Not Applicable
x64-based computers
File nameFile versionFile sizeDate (UTC)Time (UTC)Platform
Normidna.nlpNot Applicable59,34203-Aug-200619:03Not Applicable
Normnfc.nlpNot Applicable45,79403-Aug-200619:03Not Applicable
Normnfd.nlpNot Applicable39,28404-Aug-200604:03Not Applicable
Normnfkc.nlpNot Applicable66,38404-Aug-200604:03Not Applicable
Normnfkd.nlpNot Applicable60,29403-Aug-200619:03Not Applicable
IA-64-based computers
File nameFile versionFile sizeDate (UTC)Time (UTC)Platform
Normidna.nlpNot Applicable59,34204-Aug-200604:03Not Applicable
Normnfc.nlpNot Applicable45,79403-Aug-200619:08Not Applicable
Normnfd.nlpNot Applicable39,28404-Aug-200604:03Not Applicable
Normnfkc.nlpNot Applicable66,38404-Aug-200604:03Not Applicable
Normnfkd.nlpNot Applicable60,29404-Aug-200604:03Not Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, 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
For more information about interop-debugging, visit the following Microsoft Web site:

Article ID: 923326 - Last Review: 01/17/2015 15:42:19 - Revision: 2.0

  • Microsoft .NET Framework 1.1
  • kbnosurvey kbarchive kbdebug kbcominterop kbstack kbbug kbfix kbqfe KB923326