Ordinal 3288 could not be located

I received an error after installing the latest version (9.0.12) today: "The ordinal 3288 could not be located in the dynamic link library LIBEAY32.dll". After installation, when I try to launch s-server.exe, I get the error and cannot browse to localhost:1272. I would appreciate any suggestions.

Can you do a search on your system for LIBEAY32.DLL and report the directories in which it has been found (including system folders)?

It was found in:



-WindowsTemppdk-SYSTEM-6864

-Program Files (x86)WebExProductivity Tools

-Program Files (x86)WebExConnect

-Program Files (x86)ThinkPadUtilities

-WindowsSetupPackagesEnterpriseApplicationWinx64Lenovo

-Program Files (x86)VMwareInfrastructureVirtual Infrastructure Client5.0

-Program Files (x86)Common FIlesVMwareVMware VMRC PluginInternet Explorer

-Program Files (x86)Common FilesVmwareVmware VMRC Plug-inFirefox

-Program Files (x86)iPassiPassConnectdownloader

-Program Files (x86)iPassiPassConnect

-Program Files (x86)CiscoCSAgentbin

-Program Files (x86)ServersCheck-Monitoring

-WidowsSystem32

-WindowsSysWOW64

-WindowsSetupScripts

-Program FilesAltiris

-Program Files (x86)ServersCheck_Monitoringadd-ons

-

Can you run the command "SET" from the Windows command prompt and reply with the output?

Path=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:WindowsS

WindowsPowerShellv1.0;C:Program Files (x86)QuickTimeQTSystem;C:Pr

ilesCREDANTShield v7.1

Can you rename the LIBEAY32.dll in your Windows/System32 to LIBEAY32.OLD.dll ? Some other software must have installed it there causing a conflict as first environment paths are checked and then only local folder (Windows design)

Could you also send me the full PATH information since it seems to be truncated:



Path=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:WindowsS

WindowsPowerShellv1.0;C:Program Files (x86)QuickTimeQTSystem;C:Pr

ilesCREDANTShield v7.1

I ran s-server.exe in capability mode as Windows XP (SP3) and it was able to function properly. However, when I added my sensor gateway and the external probe, I'm unable to retrieve any data. Not sure if this is related.

Also after doing a firmware update and changing the mac address as told to do, I can no longer access the sensor nor ping it.