Mentioned
In
|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
FIX: Incorrect methods are called when you call some COM APIs that are included in a .NET Framework 2.0-based 64-bit application| Article ID | : | 947148 | | Last Review | : | June 4, 2008 | | Revision | : | 1.0 |
On This PageSYMPTOMSConsider the following scenario: | • | A 64-bit application that is created by using the Microsoft .NET Framework 2.0 calls some COM APIs. | | • | The COM APIs have multiple instances of the same method. | | • | The method uses the lcid attribute. | | • | You use one of the following to call the COM APIs:| • | The managed COM interop | | • | Platform Invoke (P/Invoke) code |
|
In this scenario, incorrect methods are called. For example, consider the following scenario: | • | You have a 64-bit application that uses a 64-bit version of common language runtime (CLR). | | • | The application has two managed P/Invoke functions that have the same signature. The signature points to a single native method. | | • | The two P/Invoke functions rely on the LCIDConversionAttribute class for localization support. | | • | You run the application. |
In this scenario, you may receive an error message that resembles the following: System.Runtime.InteropServices.COMException (0x800706F4): A null reference pointer was passed to the stub. (Exception from HRESULT: 0x800706F4) Back to the top
RESOLUTIONHotfix informationA 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 Windows Vista or .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. PrerequisitesYou must have one of the following installed to apply this hotfix: | • | Windows Vista Service Pack 1 | | • | The .NET Framework 2.0 Service Pack 1 |
Restart requirementYou do not have to restart the computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. 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. The .NET Framework 2.0, 32-bit versions, on a computer that is not running Windows Vista| File name | File version | File size | Date | Time | Platform |
|---|
| Cordacwks.dll | 2.0.50727.1812 | 822,280 | 29-Jan-2008 | 10:48 | x86 | | Mscorlib.dll | 2.0.50727.1812 | 4,345,856 | 29-Jan-2008 | 10:48 | x86 | | Mscorwks.dll | 2.0.50727.1812 | 5,852,672 | 29-Jan-2008 | 10:48 | x86 |
The .NET Framework 2.0, Itanium-based versions, on a computer that is not running Windows Vista| File name | File version | File size | Date | Time | Platform |
|---|
| Cordacwks.dll | 2.0.50727.1812 | 822,280 | 29-Jan-2008 | 10:48 | x86 | | Cordacwks.dll | 2.0.50727.1812 | 2,769,416 | 29-Jan-2008 | 02:26 | IA-64 | | Mscorlib.dll | 2.0.50727.1812 | 4,345,856 | 29-Jan-2008 | 10:48 | x86 | | Mscorlib.dll | 2.0.50727.1812 | 3,997,696 | 29-Jan-2008 | 02:26 | IA-64 | | Mscorwks.dll | 2.0.50727.1812 | 5,852,672 | 29-Jan-2008 | 10:48 | x86 | | Mscorwks.dll | 2.0.50727.1812 | 21,686,272 | 29-Jan-2008 | 02:26 | IA-64 |
The .NET Framework 2.0, 64-bit versions, on a computer that is not running Windows Vista| File name | File version | File size | Date | Time | Platform |
|---|
| Cordacwks.dll | 2.0.50727.1810 | 1,652,744 | 14-Jan-2008 | 23:36 | x64 | | Cordacwks.dll | 2.0.50727.1812 | 822,280 | 29-Jan-2008 | 10:48 | x86 | | Mscorlib.dll | 2.0.50727.1810 | 4,345,856 | 14-Jan-2008 | 23:36 | x64 | | Mscorlib.dll | 2.0.50727.1812 | 4,345,856 | 29-Jan-2008 | 10:48 | x86 | | Mscorwks.dll | 2.0.50727.1810 | 10,547,200 | 14-Jan-2008 | 23:36 | x64 | | Mscorwks.dll | 2.0.50727.1812 | 5,852,672 | 29-Jan-2008 | 10:48 | x86 |
The .NET Framework 2.0 on a computer that is running a 32-bit version of Windows Vista with Service Pack 1| File name | File version | File size | Date | Time | Platform |
|---|
| Mscorlib.dll | 2.0.50727.1826 | 4,345,856 | 06-May-2008 | 22:18 | x86 | | Mscordacwks.dll | 2.0.50727.1826 | 822,280 | 06-May-2008 | 22:18 | x86 | | Mscorwks.dll | 2.0.50727.1826 | 5,852,672 | 01-May-2008 | 23:34 | x86 |
The .NET Framework 2.0 on a computer that is running a 64-bit version of Windows Vista with Service Pack 1| File name | File version | File size | Date | Time | Platform |
|---|
| Mscorlib.dll | 2.0.50727.1826 | 4,345,856 | 05-May-2008 | 22:13 | x64 | | Mscordacwks.dll | 2.0.50727.1826 | 1,652,744 | 05-May-2008 | 22:13 | x64 | | Mscorwks.dll | 2.0.50727.1826 | 10,543,104 | 01-May-2008 | 23:36 | x64 | | Mscorlib.dll | 2.0.50727.1826 | 4,345,856 | 06-May-2008 | 22:18 | x86 | | Mscordacwks.dll | 2.0.50727.1826 | 822,280 | 06-May-2008 | 22:18 | x86 | | Mscorwks.dll | 2.0.50727.1826 | 5,852,672 | 01-May-2008 | 23:34 | x86 |
Back to the top
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Back to the top
MORE INFORMATIONFor more information about P/Invoke, visit the following Microsoft Developer Network (MSDN) Web site: For more information about the
lcid attribute, visit the following MSDN Web site: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684 (http://kbalertz.com/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates Back to the top
APPLIES TO| • | Microsoft .NET Framework 2.0 |
Back to the top
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
|
 |
 |
 |
 |
 |
 |
 |
| |