Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: A debug assertion occurs when a Windows Forms control is hosted on an MFC form in Visual Studio .NET 2003
Article ID: 824647 - View products that this article applies to.
In Microsoft Visual Studio .NET 2003, if a Microsoft Windows Forms control is hosted on a Microsoft Foundation Classes (MFC) form, a debug assertion occurs at line 955 in the Occcount.cpp file. If you ignore this assertion, an access violation error occurs.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Visual Studio .NET 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. 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=supportNote 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 English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------- 17-Jul-2003 23:22 56,223 Afx.h 31-Jul-2003 00:14 319,746 Eafxis.lib 31-Jul-2003 00:14 310,120 Eafxisd.lib 31-Jul-2003 00:58 7.10.3211.0 1,060,864 Mfc71.dll 31-Jul-2003 00:17 7.10.3211.0 2,183,168 Mfc71d.dll 31-Jul-2003 00:50 7.10.3211.0 1,048,064 Mfc71u.dll 31-Jul-2003 00:18 7.10.3211.0 2,177,536 Mfc71ud.dll 31-Jul-2003 00:14 16,909,318 Nafxcw.lib 31-Jul-2003 00:14 17,040,404 Nafxcwd.lib 31-Jul-2003 00:14 129,138 Nafxis.lib 31-Jul-2003 00:14 132,454 Nafxisd.lib 17-Jul-2003 23:19 6,073 Objcore.cpp 18-Jul-2003 00:21 24,323 Occcont.cpp 31-Jul-2003 00:16 17,208,136 Uafxcw.lib 31-Jul-2003 00:16 17,432,170 Uafxcwd.lib
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 824647 - Last Review: October 25, 2005 - Revision: 1.6