Unable to run 32 bit Com component in 64 bit machine

Hello All,

I am unable to run 32 bit com component references using my active directory code in the 64 bit machine.

I am getting below error message :

0x800a01ad - Microsoft VBScript runtime error: ActiveX component can't create object

Error in the below line source code :

' Create the component

Set oSoapClient = Server.CreateObject( "MSSOAP.SoapClient30" ) (error message in this line)

' Config the object

oSoapClient.ClientProperty( "ServerHTTPRequest" ) = True

oSoapClient.mssoapinit g_sADAddress & "?WSDL", ""

Kindly help me to over come this issue need work this 64 bit machine.

A while ago I ran into a problem while working on a 64bit application. I needed to use a 32bit COM object in my 64bit application but alas that didn’t work.

It seems that by default 32bit COM objects are not usable in a 64bit environment. Trying to access a 32bit COM in a 64bit environment will result in a class not registered error. However, this can be countered using dllhost as a surrogate for the 32bit COM object.

To do this, it involves a small number of simple registry hacks:

Locate your COM object GUID under the HKey_Classes_Root\Wow6432Node\CLSID\[GUID]

Once located add a new REG_SZ (string) Value. Name should be AppID and data should be the same COM object GUID you have just searched for

Add a new key under HKey_Classes_Root\Wow6432Node\AppID\

The new key should be called the same as the com object GUID

Under the new key you just added, add a new REG_SZ (string) Value, and call it DllSurrogate. Leave the value empty

Create a new Key under HKey_Local_Machine\Software\Classes\AppID\

Again the new key should be called the same as the COM object’s GUID. No values are necessary to be added under this key.

That’s it, your COM Object should now be accessible from a 64bit environment and can be used like a regular COM Object.

Hope this helped you out. If you have any questions feel free to leave a comment and I will try to help if possible.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Madan Shekar7y ago
A while ago I ran into a problem while working on a 64bit application. I needed to use a 32bit COM object in my 64bit application but alas that didn’t work.
It seems that by default 32bit COM objects are not usable in a 64bit environment. Trying to access a 32bit COM in a 64bit environment will result in a class not registered error. However, this can be countered using dllhost as a surrogate for the 32bit COM object.
To do this, it involves a small number of simple registry hacks:
Locate your COM object GUID under the HKey_Classes_Root\Wow6432Node\CLSID\[GUID]
Once located add a new REG_SZ (string) Value. Name should be AppID and data should be the same COM object GUID you have just searched for
Add a new key under HKey_Classes_Root\Wow6432Node\AppID\
The new key should be called the same as the com object GUID
Under the new key you just added, add a new REG_SZ (string) Value, and call it DllSurrogate. Leave the value empty
Create a new Key under HKey_Local_Machine\Software\Classes\AppID\
Again the new key should be called the same as the COM object’s GUID. No values are necessary to be added under this key.
That’s it, your COM Object should now be accessible from a 64bit environment and can be used like a regular COM Object.
Hope this helped you out. If you have any questions feel free to leave a comment and I will try to help if possible.
+1