Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ordinal 535 could not be located #224

Open
OverloadC14 opened this issue Oct 19, 2018 · 26 comments

Comments

Projects
None yet
9 participants
@OverloadC14
Copy link

commented Oct 19, 2018

Returns the error "The ordinal 535 could not be located in the dynamic link library C:\Windows\system32\ssleay32.dll." upon launch of current version of launcher, then crashes upon pressing OK.
Version 1.3.11.1 is the last version I can run without this error. Am running Windows 8.1 and have reinstalled Microsoft Visual C++ 2015 in an attempt to trouble shoot.

@RosieMcCattail

This comment has been minimized.

Copy link

commented Oct 19, 2018

Am I having the similar problem?
'The program can't start because api-ms-win-core-localization-l1-2-0.dll is missing from your computer'

Googling it revealed that this file is a part of Microsoft Visual C++ 2015, but downloading and installing both x64 and x86 versions did not help.
(Win7 x64)

@remyroy

This comment has been minimized.

Copy link
Owner

commented Oct 19, 2018

I'm not sure what the issue is here. Both api-ms-win-core-localization-l1-2-0.dll and ssleay32.dll are distributed with the release binary.

Which version(s) are you having issues with?

@Styxx42

This comment has been minimized.

Copy link

commented Oct 19, 2018

I am only able to run Version 1.3.11.1
Both versions after the above give me the same error with 354 ordinal error.
And I did redownload MSVc++ from your link in the download page and ran it with Admin rights.
I put mine in because the error number and file names were different. I didn't want to do a ME TOO.
I am win 7 64.
I wouldn't even bother you except the update feature of 1.3.11.1 has stopped working suddenly after you released you last version. Did you change something to stop 1.3.11.1 from being able to update CDDA or is this possibly a clue as to why this error is coming up.

@RosieMcCattail

This comment has been minimized.

Copy link

commented Oct 20, 2018

Which version(s) are you having issues with?

The latest, 1.3.15.
The version I'm running now is 1.3.10, but the game updates are no longer avaliable.

@remyroy

This comment has been minimized.

Copy link
Owner

commented Oct 20, 2018

Can you try installing this and see if it fixes this issue? https://aka.ms/vs/15/release/VC_redist.x86.exe

@zakhad

This comment has been minimized.

Copy link

commented Oct 20, 2018

I've done that and i still get the same error. via installing https://aka.ms/vs/15/release/VC_redist.x86.exe.
I'm also on win 7 64bit.

@Styxx42

This comment has been minimized.

Copy link

commented Oct 20, 2018

I tired as well with a reboot after I installed it.
Same issue. Ordinal error then the launcher crashes.

So did you intentionally disable updating cdda with the older versions?
It is a way to force us to update to newest version?
Or is it indicative of this issue and a possible clue?
I have disabled my AV, made sure my firewalls are off. This happens on three different computers of mine. Or all my computers. Two laptops, one desktop.
I am willing to test and try more options. Let me know what else I can do to assist troubleshooting this..

@RosieMcCattail

This comment has been minimized.

Copy link

commented Oct 21, 2018

Same with me. I also tried installing an x64 version of Visual C++ 2017.
No results.

@willkydd

This comment has been minimized.

Copy link

commented Oct 22, 2018

I get the message variant with "The ordinal 354 could not be located in the dynamic link library ssleay32.dll", but that's no wonder since that dll doesn't actually exist in system32. What should I do? I run Windows 10 Pro 64-bit.

@remyroy

This comment has been minimized.

Copy link
Owner

commented Oct 22, 2018

It seems like there might be multiple version of those libraries and some of them might be older causing this problem. This is what I could find out by doing a quick google search.

There might be a way to fix this by modifying the way the binary is bundled. I'll see what I can do.

@remyroy

This comment has been minimized.

Copy link
Owner

commented Oct 22, 2018

@willkydd

This comment has been minimized.

Copy link

commented Oct 22, 2018

Can you test this new bundle? https://www.dropbox.com/s/8e7cl0d8j9rmt5u/test-launcher.zip?dl=1

Thanks. Tried, but getting the same error.

@remyroy

This comment has been minimized.

Copy link
Owner

commented Oct 22, 2018

This is likely to need some more investigation maybe with some virtual machines so I can reproduce the issue on my side.

@willkydd

This comment has been minimized.

Copy link

commented Oct 22, 2018

@Styxx42

This comment has been minimized.

Copy link

commented Oct 22, 2018

I tried the test launcher as well just in case.
Same Ordinal 354 error.
Then crash.

@zakhad

This comment has been minimized.

Copy link

commented Oct 28, 2018

I tried a few things i'm not sure which one worked but i think it was deleting the LIBEAY32.dll dll inside the win 32 folder (Win 7 64bit) that acutally worked in the end for me but i also downloaded https://slproweb.com/products/Win32OpenSSL.html before (I installed both 32bit/64bit) I was just trying everything under the sun to get it to work it struck me as something was wrong with my end rather than the launcher since it was only a handful of people who had this problem

But yeah, i'm able to run 1.3.15 now perfectly fine

@willkydd

This comment has been minimized.

Copy link

commented Oct 28, 2018

I tried a few things i'm not sure which one worked but i think it was deleting the LIBEAY32.dll dll inside the win 32 folder (Win 7 64bit) that acutally worked in the end for me but i also downloaded https://slproweb.com/products/Win32OpenSSL.html before (I installed both 32bit/64bit) I was just trying everything under the sun to get it to work it struck me as something was wrong with my end rather than the launcher since it was only a handful of people who had this problem

But yeah, i'm able to run 1.3.15 now perfectly fine

Tried installing win32openSSL. Same error.
Tried removing libeay32.dll and couldn't because I didn't have such a file to begin with.

What else did you do @zakhad?

@zakhad

This comment has been minimized.

Copy link

commented Oct 28, 2018

I think i installed Visual C++ 2017.as well, both 32 and 64bit, as well as the 2015 variants, pretty much tried everyone to see if it'd help, but i'm fairly certain it wasn't them, it was quite literally the last thing i did was delete that LIBEAY32 file i,e to see if i got a corrupted file and reinstall the previously mentioned in here things.

I did notice that there is a similar issue with another program and some found a workaround/hack but I've no idea if'it'd work.

uglide/RedisDesktopManager#3980

@Taberone

This comment has been minimized.

Copy link

commented Nov 12, 2018

Still getting the error too, but it says ordinal 354 instead or something.

@HISVee

This comment has been minimized.

Copy link

commented Dec 15, 2018

Still having this issue in the latest update with ordinal 354

@Saint-of-Grey

This comment has been minimized.

Copy link

commented Mar 26, 2019

Just ran into the same issue but with ordinal 353, and thought I could provide some insight on it with how I fixed it.

I did some digging and found I had a copy of the openssl libraries from 2003 installed in C:\Windows\System (not System32). I replaced those with modern versions and the launcher worked.

Given how... dodgy fiddling with system directories is, I didn't test if it would work if I deleted them, but I bet that has something to do with the intermittency of this issue.

@remyroy

This comment has been minimized.

Copy link
Owner

commented Mar 31, 2019

@Saint-of-Grey I was suspecting something similar. Thanks for the information.

@Taberone

This comment has been minimized.

Copy link

commented Apr 16, 2019

Just ran into the same issue but with ordinal 353, and thought I could provide some insight on it with how I fixed it.

I did some digging and found I had a copy of the openssl libraries from 2003 installed in C:\Windows\System (not System32). I replaced those with modern versions and the launcher worked.

Given how... dodgy fiddling with system directories is, I didn't test if it would work if I deleted them, but I bet that has something to do with the intermittency of this issue.

May I ask how you replaced it with a modern version? Where did you get it from? Tried to look in C\Windows\System but it's empty, too.

EDIT: Did a search in my C: Drive for LIBEAY32. It's everywhere. What the hell? Which one do I delete so I can finally stop getting this stupid "Ordinal could not be located" error?

2019-04-16 08_08_53-LIBEAY32 - Search Results in Local Disk (C_)

Getting a new OpenSSL from https://slproweb.com/products/Win32OpenSSL.html didn't work, either.

@Saint-of-Grey

This comment has been minimized.

Copy link

commented Apr 24, 2019

I recall reading somewhere you want the libraries from 1.0.2, not 1.1.0. But honestly, I have no idea which libraries it's trying to use on your setup, maybe the ones in SysWOW64? Those look like they're a decade old.

@Taberone

This comment has been minimized.

Copy link

commented Apr 26, 2019

@Saint-of-Grey Thank you! Installing 1.0.2 libraries and replacing the ones that exist in SysWOW64 worked.
@remyroy Possible solution found. Install 1.0.2 libraries of Win32OpenSSL

@RosieMcCattail

This comment has been minimized.

Copy link

commented May 5, 2019

All right, so I'm back and the problem is still with me. The latest release of the launcher just won't start, because 'api-ms-win-core-localization-l1-2-0.dll is missing from your computer'.
I've tried uninstalling Visual C++ 2017 packages (both x64 and x86) and replacing them with 2015 versions. As expected, it did not help.
I've then found this thread and read through it. Since my PC lacked libeay32.dll file(s), I've downloaded the win32openssl from that link above. That did not help. I've then downloaded win64openssl from that link and also installed it. That did not help.

Then the brightest idea to actually check the system folders came to my mind and, as expected, there was no such file as api-ms-win-core-localization-l1-2-0.dll in neither system32 nor syswow64.
So can anybody tell me why is it not being written from any of the Visual C++ installation packages?

I really do not want to download this file alone from some shady sites. If this file is included into the Visual C++ package, it should get installed from the package, right?

Okay, so here is this file where it is present. Should I just copy one of the versions into the system folders? Seems obvious for me that those guys have been installed by other apps. The VC2015/2017 packages fail to install it.

2725

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.