You may experience this problem, when can’t run TIBCO Administrator, Hawk, BW process or any other TIBCO component. In log files you can find messages related to OpenSSL libraries libeay32.dll and ssleay32.dll. The reason is that TIBCO messaging components use OpenSSL, but other applications may also use OpenSSL and have already installed these dlls in C:\WINDOWS\System32 or C:\WINDOWS\SysWOW64 depending on the platform.
When you start the application, it unsuccessful attempts to find dll files near the binary, then tries to find in the System32 folder. But dlls from other version of OpenSSL are there. Your application will use it, instead correct version from TIBCO Rendezvous bin folder for example, even you have this folder in the PATH. TIBCO product can’t call the necessary functions, gives an error and stops working.
Solution is take libeay32.dll and ssleay32.dll from TIBCO Rendezvous bin folder to the bin folders of every installed TIBCO component. Or just copy and replace to C:\WINDOWS\System32 or C:\WINDOWS\SysWOW64.











1. Comment by abhishek bhatia
2/Mar/2010 at 8:39 pm
I have similar problem but with another dll file. It is msvcr80.dll. The Hawk display or configuration screen does not open up. There is no such dll present in system32 folder or bin folders in hawk/rv. Any thoughts?
2. Comment by Serge
2/Mar/2010 at 8:59 pm
Hi! Thanks for your question.
This dll from required Microsoft Visual C++ 2005 (VC8) runtime.
You have to download and install appropriate32 bit or 64 bit VC8 redistributable.
3. Comment by abhishek bhatia
3/Mar/2010 at 1:54 am
Thanks!! I will try this out today.
4. Comment by abhishek bhatia
7/Mar/2010 at 1:02 am
Hi, I checked and found that I already have this distributable installed on my system.
- Reinstalling this did not fix the issue. I am still not able to find the correct msvcr80.dll for running Hawk display/Configuration.
- Reinstalling Tibco suite did not help either.
Is there something else that comes to your mind?
Thanks
Abhishek
5. Comment by Serge
7/Mar/2010 at 10:22 am
X64? The best way to fix “dll not found” issue is to have procmon running on your system. Then you can find which dll and where your app needs.
6. Comment by abhishek bhatia
10/Mar/2010 at 2:16 am
I will try using procmon to find out what is wrong. I am sure there is some issue with vc++ libraries.
It is a 32-bit pc, so 64 won’t help, I guess.