The fact that renaming it makes things work OK seems to point out a versioning issue. This file is based on SSLEAY, from which OpenSSL is derived. It looks like each U2 DBMS product and UniDK installs its own version of this u2libeay32.dll and u2ssleay32.dll too. By commenting one file out, you're causing Windows to search further up the executable PATH for another file by that name, and it's apparently finding one that it likes better. Your third-party products may rely on an older version of this DLL, and you are accidentally providing it somewhere up the path. OR - your third party products require a more recent version and you somehow had an older version installed which you renamed to .old. I have two versions of that file on my system too. It might help some of our colleagues here if you could identify the products and the files that they choke on, so that no one else trips on this - the product vendor(s) may be interested as well.
HTH, Tony Gravagno Nebula Research and Development TG@ removethisNebula-RnD .com Brian Leach brian-at-brianleach.co.uk |U2UG| wrote: > Bjorn, > > A quick look with Dependency Walker shows it is exporting > a set of functions for SSL, RSA encryption and > certificate (X509) services. > > So I guess it is part of the UniVerse SSL support. > > Brian > Bjorn Behr wrote: >> Can anybody tell me what this file does, as it has caused >> some problems with 3rd party products and when we rename >> it to u2libeay32.old, all seems to work, I am just worried >> that I might have missed something. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
