Article ID: 935678 - Last Review: October 8, 2011 - Revision: 2.0
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
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
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.
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.
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.
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, x86-based versions
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscordacwks.dll
2.0.50727.827
802,304
03-Apr-2007
07:54
x86
Mscorjit.dll
2.0.50727.827
326,656
03-Apr-2007
07:54
x86
Mscorlib.dll
2.0.50727.827
4,308,992
03-Apr-2007
07:54
x86
Mscorpe.dll
2.0.50727.827
102,912
03-Apr-2007
07:54
x86
Mscorwks.dll
2.0.50727.827
5,634,048
03-Apr-2007
07:54
x86
Normalization.dll
2.0.50727.827
15,360
03-Apr-2007
07:54
x86
Normidna.nlp
Not Applicable
59,342
03-Apr-2007
07:54
Not Applicable
Normnfc.nlp
Not Applicable
45,794
03-Apr-2007
07:54
Not Applicable
Normnfd.nlp
Not Applicable
39,284
03-Apr-2007
07:54
Not Applicable
Normnfkc.nlp
Not Applicable
66,384
03-Apr-2007
07:54
Not Applicable
Normnfkd.nlp
Not Applicable
60,294
03-Apr-2007
07:54
Not Applicable
Peverify.dll
2.0.50727.827
136,192
03-Apr-2007
07:54
x86
Sos.dll
2.0.50727.827
382,464
03-Apr-2007
07:54
x86
Vsavb7rt.dll
8.0.50727.827
1,330,688
03-Apr-2007
07:54
x86
The Microsoft .NET Framework 2.0, x64-based versions
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscordacwks.dll
2.0.50727.827
1,597,440
02-Apr-2007
23:54
x64
Mscordacwks.dll
2.0.50727.827
802,304
03-Apr-2007
07:54
x86
Mscorjit.dll
2.0.50727.827
1,588,224
02-Apr-2007
23:53
x64
Mscorjit.dll
2.0.50727.827
326,656
03-Apr-2007
07:54
x86
Mscorlib.dll
2.0.50727.827
4,308,992
03-Apr-2007
07:54
x86
Mscorlib.dll
2.0.50727.827
3,960,832
03-Apr-2007
03:13
x64
Mscorpe.dll
2.0.50727.827
157,184
02-Apr-2007
23:47
x64
Mscorpe.dll
2.0.50727.827
102,912
03-Apr-2007
07:54
x86
Mscorpjt.dll
2.0.50727.827
2,006,016
02-Apr-2007
23:53
x64
Mscorwks.dll
2.0.50727.827
10,335,744
02-Apr-2007
23:51
x64
Mscorwks.dll
2.0.50727.827
5,634,048
03-Apr-2007
07:54
x86
Normalization.dll
2.0.50727.827
18,432
02-Apr-2007
23:51
x64
Normalization.dll
2.0.50727.827
15,360
03-Apr-2007
07:54
x86
Normidna.nlp
Not Applicable
59,342
02-Apr-2007
23:54
Not Applicable
Normidna.nlp
Not Applicable
59,342
03-Apr-2007
07:54
Not Applicable
Normnfc.nlp
Not Applicable
45,794
02-Apr-2007
23:54
Not Applicable
Normnfc.nlp
Not Applicable
45,794
03-Apr-2007
07:54
Not Applicable
Normnfd.nlp
Not Applicable
39,284
02-Apr-2007
23:54
Not Applicable
Normnfd.nlp
Not Applicable
39,284
03-Apr-2007
07:54
Not Applicable
Normnfkc.nlp
Not Applicable
66,384
02-Apr-2007
23:54
Not Applicable
Normnfkc.nlp
Not Applicable
66,384
03-Apr-2007
07:54
Not Applicable
Normnfkd.nlp
Not Applicable
60,294
02-Apr-2007
23:54
Not Applicable
Normnfkd.nlp
Not Applicable
60,294
03-Apr-2007
07:54
Not Applicable
Peverify.dll
2.0.50727.827
205,824
02-Apr-2007
23:53
x64
Peverify.dll
2.0.50727.827
136,192
03-Apr-2007
07:54
x86
Sos.dll
2.0.50727.827
382,464
03-Apr-2007
07:54
x86
Sos.dll
2.0.50727.827
480,768
03-Apr-2007
00:01
x64
Vsavb7rt.dll
8.0.50727.827
1,330,688
03-Apr-2007
07:54
x86
The Microsoft .NET Framework 2.0, Itanium-based versions
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.