RegSvr32: LoadLibrary error (0x0000007e) 126

[Helder R. Melendez]

Does anyone know what RegSvr32: LoadLibrary error (0x0000007e) 126 is?
And is it something which affects other programs in linking to this DLL?

--------------------Configuration: weedenbase - Win32
Debug--------------------
Compiling...
SocketOrderProcessor.cpp
SocketPriceServer.cpp
SocketAlertManager.cpp
Generating Code...
Linking...
Performing registration
RegSvr32: LoadLibrary(".\Debug\weedenbase.dll") failed.
GetLastError returns 0x0000007e.
1 file(s) copied.
1 file(s) copied.

weedenbase.dll - 0 error(s), 0 warning(s)

Helder

[Guillaume Landru]

The follwing comes from winerror.h, it may help

//
// MessageId: ERROR_MOD_NOT_FOUND
//
// MessageText:
//
// The specified module could not be found.
//
#define ERROR_MOD_NOT_FOUND 126L

Cheers,
Guillaume.

"Helder R. Melendez" <hmel...@weedenco.com> wrote in message
news:39C2351D...@weedenco.com...

[Frank Oquendo]

I don't know what the error means but failure to properly register a COM
server prevents clients from using it.

--
Attitudes are contagious. Is yours worth catching?
http://www.acadx.com

[Joe O'Leary]

Whenever you see an error message like this, Run the "Error Lookup"
utility that comes with Visual C++. It will give you a string
description of what the error means. You can find it on your Tools
menu in Visual C++ IDE and in the VC program group on the Start menu.

You can also find most of these errors in WINERROR.H but ErrLook is
more convenient.

In your case, the error code means one of the modules (DLLs) required
by your COM dll is not found. The best way to determine which one it
is missing is to use another utility called DEPENDS.EXE

Depends comes in the Platform SDK, freely available from MS. You run
it and tell it to load a DLL, such as your COM DLL. It then shows you
a list of all the toher DLLs that your DLL needs in order to run. If
it cannot find one of them, it will highlight it. You'll quickly
know what's missing

Joe O'

"Helder R. Melendez" <hmel...@weedenco.com> wrote in message
news:39C2351D...@weedenco.com...
> Does anyone know what RegSvr32: LoadLibrary error (0x0000007e) 126
is?
> And is it something which affects other programs in linking to this
DLL?
>

[Helder R. Melendez]

Joe O'Leary wrote:

Thanks for your response, Joe, but the dependency walker
does not show anything obvious. I am able to look at all
the DLL's my DLL depends on and I can see the mangled
names for them. However, it does raise an interesting issue.
I can see the "unresolved external symbol" name that the linker
is complaining about when trying to link an EXE. I can see the
exact mangled name in the dependency walker for which I am
getting a LNK2001 error.

Hmm?

Helder

[Jeffrey Walton]

Hello,

Later versions of Dependency Walker allow you to profile your code. You
might try that also. The version of depends.exe that is currently installed
on my machine is 2.0, beta 5. This version will show you the libraries
required as specified in the PE header (as the old version). But when you
profile, all calls to LoadLibrary are displayed in the output window. When
profiling, select "Hook the process to gather more detailed dependency
information", and "Log LoadLibrary function calls".

Jeff
================================================

"Helder R. Melendez" <hmel...@weedenco.com> wrote in message

news:39C26149...@weedenco.com...

[Helder R. Melendez]

Jeffrey Walton wrote:

> Hello,
>
> Later versions of Dependency Walker allow you to profile your code. You
> might try that also. The version of depends.exe that is currently installed
> on my machine is 2.0, beta 5. This version will show you the libraries
> required as specified in the PE header (as the old version). But when you
> profile, all calls to LoadLibrary are displayed in the output window. When
> profiling, select "Hook the process to gather more detailed dependency
> information", and "Log LoadLibrary function calls".
>
> Jeff

How do I get this version?