Windows Server 2008: “E_ OUTOFMEMORY” error code when a COM client tries to subscribe to type change notifications on a 64-bit version of Windows Vista or of Windows Server 2008 that has sufficient memory
Posted by TechSupport
SUPPORT PROBLEM: “E_ OUTOFMEMORY” error code when a COM client tries to subscribe to type change notifications on a 64-bit version of Windows Vista or of Windows Server 2008 that has sufficient memory
Applications Supported:
COPYRIGHT NOTICE: (c) 2007 Microsoft Corporation. All rights reserved.
SUPPORT SOLUTION:
A COM client tries to subscribe to type change notifications by calling the IConnectionPoint::Advise method on an ITypeInfo instance in a 64-bit version of Windows Vista or of Windows Server 2008. However, the COM client receives an “E_ OUTOFMEMORY” error code. This issue occurs even when Windows has sufficient memory.For example, you use a 64-bit version of Microsoft Excel 2010 on a computer that is running a 64-bit version of Windows Vista or of Windows Server 2008. You use the following code to create a Microsoft Visual Basic for Application (VBA) macro in Excel, and then run the VBA macro to add 2500 worksheets in the Excel workbook. Sub sample() Dim xlbook As Workbook Set xlbook = Workbooks.Add() xlbook.Sheets(”Sheet1″).Select For i = 1 To 2500 xlbook.Sheets.Add Next i End Sub In this example, the VBA macro adds 2500 worksheets to a workbook automatically. When you run this macro in a 32-bit version of Excel 2010, the macro creates 2500 worksheets successfully. However, when you run this macro in a 64-bit version of Excel 2010, the macro creates several hundreds of worksheets and then fails. The issue occurs because of an error in the 64-bit version of Automation. Hotfix information
2, ‘resolution’);
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites
3, ‘resolution’);
To apply this hotfix, you must be running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 SP2. For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base: 935791 (http://support.microsoft.com/kb/935791/ ) How to obtain the latest Windows Vista service pack For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base: 968849 (http://support.microsoft.com/kb/968849/ ) How to obtain the latest service pack for Windows Server 2008 Restart requirement
3, ‘resolution’);
You must restart the computer after you apply this hotfix.Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace a previously released hotfix.
Corrupt BKF Backup File Repair/Recovery
Add A Comment