SSL DLL's in path

[Majodi]

I had a hard time to get the SSL examples to work. Somehow the server was not listening to the secure port. Finally I found out what the problem was by unchecking suppress errors. It turned out that it could not load libssl32.dll, libeay32.dll and msvcr71.dll.

When I copy these in the working directory (where the exe is) everything is fine. I checked the path and even tested the path, the 3rdParty/bin dir is in the path.

Someone have a clue?

Thanks,

Majodi

[Bruce]

Hi Majodi,

Having the DLL's in the path is not ideal. I strongly recommend always having them in the application directory. The 4 DLL's work together, and the ones I've seen in various paths are not always of the same version. So, as with all DLL's, having them in the application folder is a very quick way to avoid all kinds of versioning hassles.

Cheers
Bruce

[Majodi]

Bruce, you say 4 DLL's. I only copied 3. This is what I have in my 3rdParty Bin directory:

accini.exe
c60netx.dll
c6_vista_fix.exe
libeay32.dll
libssl32.dll
MakeCertificates
msvcr71.dll
openssl.exe
pwutil.dll
ssleay32.dll

Majodi

Hi Majodi,

Having the DLL's in the path is not ideal. I strongly recommend always having them in the application directory. The 4 DLL's work together, and the ones I've seen in various paths are not always of the same version. So, as with all DLL's, having them in the application folder is a very quick way to avoid all kinds of versioning hassles.

Cheers
Bruce

[Bruce]

SSL needs the following 4;

libeay32.dll
libssl32.dll
ssleay32.dll
msvcr71.dll

Cheers
Bruce

[Majodi]

Ah, thanks.

Majodi

SSL needs the following 4;

libeay32.dll
libssl32.dll
ssleay32.dll
msvcr71.dll

Cheers
Bruce

[vsorensen]

A client has reported this error with 4.31PR14:



(Unhandled exception in ... LIBSSL32.DLL 0xC000005, Access Violation)

Is it worth updating the SSL DLLs to address this?

[Bruce]

Hi Vince,

Are there any details of the crash? ie does it happen just once, or is it regular?

Cheers
Bruce

[vsorensen]

It's happened once so far.

A client was testing the latest version of my product before putting it into use; after a week of testing they were ready to rollout, but I wanted to ensure that a small change was included (the "___" to "_:" modification I make with each release), and I updated to PR14 at the same time.  They tried this build, got the error.  I've done a clean recompile, and they are trying it again today. 

If it happens again, I'll try to get more information collected.

[pierredt]

I use a tool called FileAlyzer to establish which DDL's are used in an exe.
See: http://www.snapfiles.com/get/filealyzer.html (freeware)

All DLL calls are listed the tab 'Import/Export table'