Re: BUG #5248: Cannot find SSLEAY32.dll problem.

Thanks for your response. Please see inline...

-----Original Message-----
From: Craig Ringer [mailto:craig(at)postnewspapers(dot)com(dot)au]
Sent: Friday, December 18, 2009 7:30 AM
To: Pinto, Vincent
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #5248: Cannot find SSLEAY32.dll problem.

On 17/12/2009 6:10 PM, Vincent Pinto wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5248
> Logged by: Vincent Pinto
> Email address: vincent_pinto(at)mentor(dot)com
> PostgreSQL version: 8.3.1.876
> Operating system: Windows XP SP3
> Description: Cannot find SSLEAY32.dll problem.
> Details:
>
> We have an application that installs postgres.

How? Using the OneClick installer's silent/scripted install? From the
zip files? If the latter, how and where?

<vpinto> Our application installation starts by the user double-clicking
install.exe (It is simply a 320MB install.exe, which contains all the
stuff; the db, the application files, the help files, etc). It then
installs various application files, and somewhere in this flow, I
suspect a scripted install happens of the postgres db. Once that is
done, I an attempt is made to start the database, all as part of the
script. When the db has started, some default data is loaded, so that
the user begins using the application with the data. When the db is
attempted to be started, we get the error.

> But during the install,
> while it tries to start the database, and error "This application
> failed to start because SSLEAY32.dll was not found. Re-installing the
> application may fix this problem." pops up.

SSLEAY32.DLL should be part of the PostgreSQL install and in the same
directory as the PostgreSQL binaries. Is it not?

<vpinto> Yes it is. That is what is very confusing.

> I tried reinstalling but that does not help. I also noticed on my
> earlier laptop that ssleay32.dll is not in the windows/system32 dir
> (many folks on various forums suggest to do so, but I did not do it
> because the db starts on the earlier machine, so why should it not
> start on the newer on?)

No, do *not* mess with WINDOWS\SYSTEM32 . People who tell you to install
random libraries there are almost certainly wrong, and are parroting
advice that used to apply back in the Windows 95/98 days before Windows
preferentially loaded libraries from the same directory as the
application.

<vpinto> Quite correct. I will not.

--
Craig Ringer