I am attempting to register a basic COM dll on a Windows Server 2008 standard box.
I run regsvr32 capicom.dll and it reports DllRegisterServer in capicom.dll succeeded. This is the same process we've used for years on Windows Server 2003.
Sadly, when I attempt to create the object via a very very basic Microsoft vbscript example Set oStore = CreateObject("CAPICOM.Store") it throws a "ActiveX component can't create object" error.
Thinking maybe it was a problem with this dll, I tried a few other DLLs we use with the same result. I tried using the regsvr32 in system, system32, and syswow64 all with the same result. I don't know too much about the differences between each of those, but figured it was worth a shot.
The dll is being stored on the d:\ and seems to have correct permissions (though that'd be a different error altogether).
*UPDATE: Through additional testing, we have determined (via dependency walker) that ieshims.dll and linkinfo.dll are missing. They are on the machine, but reported as could not find. This is true of both capicom.dll and an internally developed dll.
Thanks to any help or thoughts you might have!
Best Answer
It appears that wscript was running in 64 bit mode and was unable to see the registrations... following the instructions on http://forums.iis.net/t/1154189.aspx I was able to run the createobjects in 32 bit mode (via classic asp) and the components worked as they should. Thanks for the help all!