You need to find out the GUID of a COM object defined in the DLL. Then look at this registry key: HKEY_CLASSES_ROOT\CLSID\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\InprocServer32 Replace the x’s with the GUID. It should have a default value that contains the full path to the DLL.
There are not many good reasons this would fail, especially the regsvr32 step. Run dumpbin /exports on that dll. If you don’t see DllRegisterServer then you’ve got a corrupt install. It should have more side-effects, you wouldn’t be able to build C/C++ projects anymore. One standard failure mode is running this on a 64-bit operating … Read more
It turns out to get this application working under VBScript, I had to do two things. Run RegAsm.exe to register the DLLs. Run the C:\Windows\SysWOW64\cscript.exe to run my VBScript. If these don’t work, check out the other answer here about enabling 32-bit applications in IIS.
To find the DLL, go to your 64-bit machine and open the registry. Find the key called HKEY_CLASSES_ROOT\CLSID\{681EF637-F129-4AE9-94BB-618937E3F6B6}\InprocServer32. This key will have the filename of the DLL as its default value. If you solved the problem on your 64-bit machine by recompiling your project for x86, then you’ll need to look in the 32-bit portion … Read more
Try regasm /u “[full path to your DLL in double quotes]” To re-register use regasm /codebase “[full path to your DLL in double quotes]” ignore the warning.
You can do that using the gacutil tool. In its simplest form: gacutil /i yourdll.dll You find the Visual Studio Command Prompt in the start menu under Programs -> Visual Studio -> Visual Studio Tools.
Well, you don’t specify if it’s a 32 or 64 bit dll and you don’t include the error message, but I’ll guess that it’s the same issue as described in this KB article: Error Message When You Run Regsvr32.exe on 64-Bit Windows Quote from that article: This behavior occurs because the Regsvr32.exe file in the … Read more