Libeay32.dll conflict

[cwahlmeier]

I know no one will probably answer this... It looks like IBM started
including Libeay32.dll in the DB2 Client. Of course, this has put us
in DLL hell. It is conflicting with Paymentech credit card processing
software. Anyone dealt with this situation before?

Thanks,

Craig Wahlmeier

[Jan M. Nelken]

cw********@data-tronics.com wrote:

I know no one will probably answer this...
Sounds like a challenge ...
It looks like IBM started
including Libeay32.dll in the DB2 Client. Of course, this has put us
in DLL hell. It is conflicting with Paymentech credit card processing
software. Anyone dealt with this situation before?

It appears that libeay32.dll provides encryption/decryption for SSL. If you are
not using SSL - then perhaps renaming this library to something nonexecutable
(for example Libeay32dll.Ibm) may work?

Otherwise call IBM Support ...

Jan M. Nelken

[Mark Yudkin]

We're using Libeay32.dll in our application, and have had no conflicts with
the DB2 client.

The loader will first load libeay32.dll from the application's EXE's
directory. Where has Paymentech put its? If it's not in the Paymentech^s
EXE's directory, you'll need to contact them for a resolution.

<cw********@data-tronics.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

I know no one will probably answer this... It looks like IBM started
including Libeay32.dll in the DB2 Client. Of course, this has put us
in DLL hell. It is conflicting with Paymentech credit card processing
software. Anyone dealt with this situation before?

Thanks,

Craig Wahlmeier

[cwahlmeier]

Our problems came from our environment. We are running VBScript under
IIS using OLEDB to query DB2. The threading model we used caused
everything to run under dllhost. Since DB2 is heavily used, it got
loaded first.
When we split the application out to its own thread, and created the
Paymentech object first, it solved our problem.

We plan to take this a step further. We are going to run the
Paymentech software under a seperate COM object. This will fix the
problem for good.

Thanks for your replies.

Craig