Home/ Questions/Q 4626092
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T03:22:06+00:00

I’ve created a C# COM object, and am trying to instantiate it from VBscript

  • 0

I’ve created a C# COM object, and am trying to instantiate it from VBscript (under Windows Scripting Host).

The assembly builds correctly, etc, and RegAsm claims that it is successfully registered. However, whenever I try to instantiate it in a .vbs script, I get:

Error: Could not creawte object named

"MyProgId.blah" Code: 80040154

I’m running Win7 x64 Ultimate, object built for .NET 3.5 with VS2010.

I also tried copying the compiled DLL over to a Win Server 2003 machine, and I get the same results there.

Help.

Also, of note: I can register, but not instantiate, any of our old VB6 COM DLLs. (Yes, I am running the script as administrator.)

Update

Just for grins, I created a test application that uses Type.GetFromProgID() to find and create the object:

Type t = Type.GetTypeFromProgID(progId);

if (t == null)
{
    Console.WriteLine("Couldn't create object.");
}
else
{
    var obj = Activator.CreateInstance(t);

    Console.WriteLine("Successfully created Object: Type is [{0}]", obj);

    Console.WriteLine("Calling method [{0}]\n\n", methodName);

    var result = t.InvokeMember(methodName, BindingFlags.Default | BindingFlags.InvokeMethod, null, obj, null);

    Console.WriteLine("Result: {0}", result);

}

This works correctly. Attempting to create the object from VBscript, however, still fails.

Argh.

Update, the 2nd

After running SysInternals ProcMon, I see quite a few registry queries looking for the progID and guid under HKCU\Software\Classes\..., where there is no mention of the object (when I look in RegEdit). There are quite a few NAME NOT FOUND errors.

I’ve tried registering with the %windir%\microsoft.net\framework\v4... and framework64 versions of regasm, with no effect.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m running Win7 x64 Ultimate

    That’s very relevant to COM issues like these. The error message means that the COM client could not find the registry information for the COM server. The 64-bit version of Windows has two VB-script interpreters, a 64-bit and a 32-bit version. Processes with different bitness have a different view of the registry, a 64-bit client cannot see 32-bit COM servers. And the other way around.

    What matters is what version of Regasm.exe you used. There are two, one in C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe, another in Framework64. You by default run the 32-bit version which enters registration info in the 32-bit view of the registry. You should use the 64-bit version from Framework64 instead. Or use both, .NET creates COM servers that can run in both bitnesses.

    If you still have trouble then use SysInternals’ ProcMon tool to see where the script interpreter is looking for the CLSID key.

    • 0