DISP_E_PARAMNOTFOUND (0X80020004) Fix – Parameter Not Found In COM

When This Error Hits You

You're running a VBA macro in Excel, a PowerShell script automating Outlook, or maybe a C++ app using COM automation. Everything works until you hit a method call — then boom: DISP_E_PARAMNOTFOUND (0X80020004). The exact trigger? You passed the wrong number of arguments, or you omitted a mandatory parameter the COM object expects.

I've seen this most often in Excel VBA when calling a custom library's method and thinking a parameter is optional when it's not. Also pops up in PowerShell with New-Object -ComObject calls where you skip a required argument. The error text says “Parameter not found” but that's misleading — it means the COM object can't find the parameter you were supposed to send.

Root Cause In Plain English

COM objects expose methods through an interface called IDispatch (that's the “DISP” in the error). When you call a method, you send a list of parameters. The object expects specific names and positions. If you send fewer parameters than needed — or send them in the wrong order — the object throws DISP_E_PARAMNOTFOUND. It's not that the parameter value is missing; it's that the parameter itself (its name or position) isn't recognized.

Common scapegoats:

• Calling a method with named parameters but misspelling one.
• Omitting a parameter that has no default value — yes, some COM methods require all parameters even if they're optional in other languages.
• Passing a parameter of the wrong type that causes the dispatch to fail.

How To Fix It

Step 1: Identify the exact method call that fails

Your error should include a line number or stack trace. If not, add error handling to trap the call. In VBA, use On Error Resume Next with Err.Description. In PowerShell, wrap the call in a try/catch block.

Step 2: Check the method's documentation

Open the COM object's type library — in VBA, press F2 to open the Object Browser. Find the failing method. Look at the parameter list. Note each parameter's name, data type, and whether it's optional. If a parameter isn't marked [Optional] or doesn't have a default value in the signature, you must supply it.

Step 3: Pass all required parameters, in order

If you're using positional parameters, pass exactly as many as needed. If you're using named parameters, double-check spelling. Example in VBA — missing the third parameter:

' Wrong – missing third param
Set obj = CreateObject("SomeLibrary.SomeClass")
obj.DoSomething "first", "second"

Fix:

' Correct – all three params
obj.DoSomething "first", "second", "third"

Step 4: For optional parameters, pass Missing in VBA

In VBA, you can't just skip an optional parameter if it's followed by another parameter. Use the Missing keyword:

obj.DoSomething "first", Missing, "third"

In PowerShell, use $null for optional parameters that have no default.

Step 5: Verify parameter types

COM is strict about types. Passing a string where a number is expected can confuse IDispatch. Cast explicitly if needed — in PowerShell, [int]$value. In VBA, use CInt(), CStr(), etc.

Real-World Example: Outlook Automation

I once helped a colleague who was automating Outlook from Excel VBA. He called Application.CreateItem(olMailItem) but then tried to call .Send without setting the To property. That's not the same error — but a similar one: he called MailItem.Recipients.Add with only one argument, missing the Type parameter. The fix was:

Set recipient = mailItem.Recipients.Add("someone@example.com")
recipient.Type = olTo

He was passing a string without specifying the recipient type. The Add method expects two parameters internally, even though VBA shows only one in the signature. Always check the actual type library.

When The Fix Doesn't Stick

If you've matched every parameter and still get the error, suspect a corrupted COM registration. Run regsvr32 on the DLL that hosts the object, or reinstall the application that provides the COM component. On rare occasions, the IDispatch interface itself is broken — then you need an updated version of the library.

Also check for 64-bit vs 32-bit mismatch. If your VBA host (e.g., Excel 32-bit) calls a 64-bit-only COM object, you'll get weird dispatch errors. Use the Win64 conditional in VBA to load the right library.

One more thing: if you're calling a method with Invoke directly (advanced COM), verify your DISPPARAMS structure. The cArgs field must match the number of parameters you pass. One off and you get this error.

That's it. You'll find the missing parameter, fix the call, and move on. Next time this error shows up, you'll know exactly where to look.