Microsoft KB Archive/935678

= FIX: You receive an E_INVALIDARG exception when you call the IDispatchEx::GetDispID method on a managed COM component in the Microsoft .NET Framework 2.0 =

Article ID: 935678

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft .NET Framework 2.0

-



SYMPTOMS
In the Microsoft .NET Framework 2.0, you receive an E_INVALIDARG exception when you call the IDispatchEx::GetDispID method on a managed Component Object Model (COM) component. If you call the managed COM component from a scripting client, you receive the following error message:

Invalid Procedure Call or Argument

This issue occurs when you use the fdexNameImplicit flag as the grfdex parameter of the IDispatchEx::GetDispID method.



CAUSE
This issue occurs because the .NET Framework 2.0 common language runtime (CLR) does not support the fdexNameImplicit flag that is used as the grfdex parameter of the IDispatchEx::GetDispID method.



RESOLUTION
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:

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 additional support questions and issues that do not qualify for the specific update in question.

Restart information
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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 Microsoft .NET Framework 2.0, Itanium-based versions


WORKAROUND
To work around this issue, do not use the fdexNameImplicit flag as the grfdex parameter of the IDispatchEx::GetDispID method when you call the IDispatchEx::GetDispID method on a managed COM component.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about software update terminology, 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

Keywords: kbfix kbqfe kbpubtypekc kbhotfixserver KB935678

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.