[osgeo4w-dev] [osgeo4w] #484: The ordinal 3872 could not be located in the dynamic link library C:\OSGeo4W\bin\SSLEAY32.dll

[OSGeo4W]

#484: The ordinal 3872 could not be located in the dynamic link library
C:\OSGeo4W\bin\SSLEAY32.dll
-------------------------+----------------------------
Reporter:  julienPX      |       Owner:  osgeo4w-dev@…
    Type:  defect        |      Status:  new
Priority:  major         |   Component:  Installer
 Version:                |  Resolution:
Keywords:  ordinal 3872  |
-------------------------+----------------------------

Comment (by jef):

 Replying to [ticket:484 julienPX]:

 > set OSGEO4W_ROOT=C:\OSGeo4W
 > set PYTHON_ROOT=C:\Python27
 > set PATH=%PATH%;%PYTHON_ROOT%;%OSGEO4W_ROOT%\bin

 So OSGeo4W is not first in PATH and you're not using OSGeo4W's python.

 > When I start my app, I get a window with the following error:
 > "The ordinal 3872 could not be located in the dynamic link library
 C:\OSGeo4W\bin\SSLEAY32.dll"

 I suppose this is produces by an import.  Can you come up with a minimal
 example causing this?  Does it also occur when you try OSGeo4W's python?

 > Here is the end of setup.log.full in C:\OSGeo4W\var\log:
 > C:\OSGeo4W>dllupdate -oite -copy -reboot "C:\OSGeo4W\bin\ssleay32.dll"
 C:\OSGeo4W\bin\ssleay32.dll: Version=1.0.1.7
 > C:\WINDOWS\system32\ssleay32.dll: Version=0.0.0.0
 > Target does not exist, no action.

 That's actually good.  ssleay32.dll shouldn't live in system32 and doesn't
 on that machine.  Above only tries to updated it to the version that ships
 with OSGeo4W - because otherwise the version in system32 might cause
 similar problems as the above because system32 is always checked for DLL
 before the directories in PATH.

--
Ticket URL: <https://trac.osgeo.org/osgeo4w/ticket/484#comment:1>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.