Setup won't register third-party DLLs

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

David Snell - 27 Apr 2004 08:36 GMT

I have written an application using third-party DLLs and installed it on a number of computers in our office. On some machines it works fine. On others Windows Installer fails to register some of the DLLs, returning HRESULT -2147024769 (which translates as: (WIN32) Warning: The specified procedure could not be found.) If I try to register the DLLs manually using regsvr32.exe, one of the DLLs registers successfully, the others fail with the following error: 'Load Library("<DLL name>") failed. The specified procedure could not be found.

What procedure is it talking about

According to depends.exe, the DLLs which can't be registered return all of the following functions

1 DllCanUnloadNo
2 DllGetClassObjec
3 DllRegisterServe
4 DllUnregisterServer

Reply to this Message

Phil Wilson - 27 Apr 2004 19:29 GMT

DllRegisterServer is that one that regsvr32 (and other install tools) needs.
If it works on some machines, it sounds like it might be an issue with
dependent DLLs, despite that message. If it's a custom-written
DllRegisterServer (rather than a default one generated by wizards etc) the
code might be trying to call some other function in another DLL and it finds
the DLL but not the function. Can't the supplier help?

Signature

Phil Wilson [MVP Windows Installer]
----

> I have written an application using third-party DLLs and installed it on a number of computers in our office. On some machines it works fine. On

others Windows Installer fails to register some of the DLLs, returning
HRESULT -2147024769 (which translates as: (WIN32) Warning: The specified
procedure could not be found.) If I try to register the DLLs manually using
regsvr32.exe, one of the DLLs registers successfully, the others fail with
the following error: 'Load Library("<DLL name>") failed. The specified
procedure could not be found.'

> What procedure is it talking about?
>
[quoted text clipped - 4 lines]
> 3 DllRegisterServer
> 4 DllUnregisterServer

Reply to this Message

David Snell - 29 Apr 2004 06:06 GMT

Thanks, but I think the DLLs are a red herring. I tried to re-compile a previously-working version, and it won't work

See "Visual Studio produces corrupted setup files".

Reply to this Message

Rate this thread:

Setup won't register third-party DLLs

Free Magazines