Gary,

since you mentioned that you call LoadLibrary() in your code, depwalker will not find those SSL DLLs for your app itself.

However, looking at your problem it may very well be that the SSL DLLs themselves do not properly initialize: they may also need additional DLL for their C run-time environment, which may fail to be available on your system.

Simply put:

you app should already fail to start when the trouble is with DLLs that are loaded at app startup time, i.e. the ones found by depwalker. This does not happen according to your description, so we'll have to inspect the LoadLibrary()-loaded DLLs themselves.

So instead you'll need to load each of the SSL DLLs in depwalker and see what depwalker reports then (you should be able to load the libeay32.dll instead of your_app.exe and see a similar dependency tree, now for the given DLL: expect errors here!).

I suspect the error is in the dependencies for the SSL DLLs themselves I expect one or more DLLs reported missing here.



This problem is well known - or should I say: well feared - and at a certain point everyone starts to perform voodoo magic (try with DLL 'x').


When depwalker reports 'all clear', there may still be an issue with
1) the build mode (static versus dynamic, release versus debug run-time libraries), and 2) manifests, but let's just pray things are resolved before you get there. :-(

ad 1): make sure your app itself and the SSL DLLs all report the same set of Microsoft run-time DLLs in their dependency tree. Things *may* work when both sets differ, but YMMV - I seem to recall that SSL is 'heap allocation clean' in the sense that anything allocated in the SSL code is also to be free()d by it, but I am not 100% sure. Anyway, that a hurdle to jump only _after_ you've resolved the DLL load issue.


Best regards,

Ger






gary clark wrote:
Hello,

I ran the dependency walker and performed a profile.

The see the error Message

"Failure to starting the process. The application has
failed to start because the application configuration
is incorrect"

Whats interesting I dont see the ssleay.dll or
libeay32.dll?
Am I suppose to? I wanted to load these dynamically?
Can they be loaded dynamically using LoadLibrary?

When I run it on the installed openSSL machine no
problem.

Thanks,
Garyc
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to