Eagle libeay32.dll problem not really fixed!!!!

[Anonymous]

Hi,

There was a post about Eagle crashing because of libeay32.dll being incorrect and the "official" fix was using some general guide on a Cyberlink page and other pages, which gave the file to download and replace it. This did fix the crashing but "Going online" and managed libraries/download problems are coming up.

Multiple times Eagle doesn't go online and when pressing the option on the Control Panel window it sometimes goes online and sometimes not, and when it goes there is also this error appearing on the bottom of the Library Manager.

Could we get an actual fix from a dev?

[Anonymous]

Version 9.1.2 just installed and this is still a problem, below is a copy of the general info from Event Viewer.

Faulting application name: eagle.exe, version: 0.0.0.0, time stamp: 0x5b63cce3
Faulting module name: LIBEAY32.dll, version: 1.0.2.7, time stamp: 0x56d84c65
Exception code: 0xc0000005
Fault offset: 0x000000000000ca23
Faulting process id: 0x23f8
Faulting application start time: 0x01d430c116d9e6f6
Faulting application path: C:\Program Files\Autodesk\EAGLE 9.1.2\eagle.exe
Faulting module path: C:\Program Files\Autodesk\EAGLE 9.1.2\LIBEAY32.dll
Report Id: 3db908dd-b7e0-4680-989e-4456cb127642
Faulting package full name:
Faulting package-relative application ID: 

[jorge_garcia]

Hi @Anonymous,

I hope you're doing well. What you are seeing is actually separate from the libeay32.dll issue. We are observing that with other users. If EAGLE won't go online then we recommend that you sign out and then sign back in. This usually solves the problem. Our devs are looking into it though.

Let me know if there's anything else I can do for you.

Best Regards,

[Anonymous]

The main problem here is that Eagle won't start unless I replace the file with one I can find from the OpenSSL installation, after that Eagle might or might not Go Online. This happens only on my laptop which has a more clean installation of Windows, while on my main PC which has been around for way longer it doesn't.

Oscar

[jorge_garcia]

Hello Oscar,

I hope you're having a good day. Maybe there is something unique about your laptop. We are running into some annoying login issues which we are investigating perhaps your laptop is affected by them.

We will continue to investigate.

Please let me know if there's anything else I can do for you.

Best Regards,

[Anonymous]

I do not think it has anything to do with the laptop.
There is simply a big bug in Eagle (also 9.1.3) as shown below.

This needs a proper fix as you cannot start Eagle.

Faulting application name: eagle.exe, version: 0.0.0.0, time stamp: 0x5b73a63f
Faulting module name: LIBEAY32.dll, version: 1.0.2.7, time stamp: 0x56d84c65
Exception code: 0xc0000005
Fault offset: 0x000000000000ca23
Faulting process id: 0x3604
Faulting application start time: 0x01d44df6dd843849
Faulting application path: C:\EAGLE 9.1.3\eagle.exe
Faulting module path: C:\EAGLE 9.1.3\LIBEAY32.dll

[one-of-the-robs]

---

@Anonymous wrote:

I do not think it has anything to do with the laptop.
There is simply a big bug in Eagle (also 9.1.3) as shown below.

This needs a proper fix as you cannot start Eagle.

---

No, you're fixated on one thing and paying no attention to what Jorge told you.

The libeay32 thing is a bug or corruption in libeay32 (part of Windows) which can be fixed by installing a correct version. This is not an Autodesk / Eagle file so it's not reasonable to ask them to fix it, especially when they have told you where to find the fix.

Then you have a second issue, which is that Eagle sometimes can't find the server to go online. This is nothing to do with libeay32 - it affects people who have never seen that other problem and does not affect lots of people who fixed libeay32 - but is a completely separate, independent, other thing, nothing to do with the first. Autodesk are working on this second issue but it's proving elusive.

[Anonymous]

I don't recommend taking an "I am 100% sure" stand when you haven't researched the matter, your "Advocate" and "Expert Elite" badges you got from an automated system don't mean anything to me with your attitude.

Libeay32 is not part of Windows, it's part of OpenSSL, nothing to do with Microsoft, the file is in Eagles program folder, it is installed by Eagle, no complicated program in the world is 100% written by the developer, all of them use sometimes open source, sometimes licensed parts, if the file they have has been corrupted or is old on some part that makes it crashing on some computers and it is not changed to a fresh copy, the problem will just exist, and since replacing the file seems to fix atleast the startup problem, that must be the case. I would have accepted the solution if it was "Here is a download link from an Autodesk server with the file that should work", and I shouldn't have to replace the file after each update.

[rachaelATWH4]

---

@Anonymous wrote:

I don't recommend taking an "I am 100% sure" stand when you haven't researched the matter, your "Advocate" and "Expert Elite" badges you got from an automated system don't mean anything to me with your attitude.

---

I don't think @one-of-the-robs has said he's 100% sure in any of his posts on this thread. With regards to the badges, yes the "Advocate" badge is auto generated from the system but the "Expert Elite" badge is not. That is by invitation only by Autodesk staff, in this case I think it would have been Jorge Garcia who invited him as he's been using EAGLE for donkeys years and has some pretty in depth knowledge of how to use it.

With regards to this issue, it seems there are specific instances where people have this issue crop up and unfortunately you appear to be one of the unlucky people who have this problem but the vast majority of people don't so I'm not 100% convinced it's all down to Autodesk, there must be other factors at play here. Certainly if they could just update the dll in their default install and fix the problem with no side effects for anybody else they would have done so by now.

Best Regards,

Rachael

[jorge_garcia]

Hi @Anonymous,

I hope you're doing well. @one-of-the-robs has earned his Elite status because as Rachael said he has been using EAGLE for "donkey's years". He may have been incorrect on the origin of Libeay32, but we can forgive that since he is predominantly a Linux user 🙂 The rest of his response was correct though, if it was simply a matter of a bad file then every Windows user would have this issue and that is not the case. Some combination of hardware and software must come together for this failure to occur. We recommend the installation of OpenSSL as a workaround because it is a safe way of getting the libeay32.dll.

I'm happy you have found a workaround but that doesn't give us an answer as to what exactly is going on. I've pinged our developers to see if they can further comment on this issue.

Let me know if there's anything else I can do for you.

Best Regards,

[nirmitiboard]

I had same problem. I downloaded latest libeay32.dll from https://www.dll-files.com/libeay32.dll.html.

then replaced old  libeay32.dll with new one in eagle installation folder

This solved the problem.

[strange_v]

The same issue, the same fix...

[Anonymous]

Thanks Sir

[anonym.mynona]

Hi @jorge_garcia,

I have the same issues but I saw now an "official" advisory on how to fix it: 

https://knowledge.autodesk.com/support/eagle/learn-explore/caas/sfdcarticles/sfdcarticles/Error-crea...

However, I am really struggling downloading DLL files from a Sketchy Website, where I cannot confrim, if the file I am looking maybe has been replaced with Malware. 

Could you let me know if there is a plan to do a minor new release of Eagle with the Correct DLLs as it seems it is a bug in Qt. 

Thanks in advance. 

Cheers,

Benny

[jorge_garcia]

Hi @anonym.mynona ,

I hope you're doing well. If you are concerned about downloading those files, one workaround is to install another program that contains them. The first example that comes to mind is to install the Windows client for Github. Once it's installed you can try copying the dlls from the github installation to EAGLE or just deleting the libeay32.dll from EAGLE may solve the issue.

Let me know if there's anything else I can do for you.

Best Regards,

[anonym.mynona]

Hi @jorge_garcia,

I am doing fine, I hope you as well.

Thanks for the help. It didn't work with Github as they removed the DLL as well (Maybe for similar reasons) but I found something different, so it worked out in the end. 

However, when you Devs know there is a faulty DLL in your Software which can be replaced with a working one, I would still be keen to see a new release which fixes the issue 🙂 

Have a good weekend ahead. 

Cheers

Benny

[mklute]

I find it hard to understand how four years later, a supposedly professional software package is linking to DLLs that were deprecated even years before they released their package. The Eagle interface is great but directing people to download 5+ years old deprecated SSL DLLs is just completely unprofessional. SSL is used for security and is updated constantly, but AutoDesk can't be bothered to re-link their package to the correct UPDATED DLLs.

Sorry, that is just sad.

[anonym.mynona]

Hi @jorge_garcia , 

Hope you are well. had you been able to chat with your Devs on when the community can expect Eagle to be updated with the working DLLs? 

Thanks in advance.

Cheers

[jorge_garcia]

Hi @anonym.mynona,

I hope you're doing well. I've reported this to them before but so far I don't have any ETA on if/when such a release may come. If anything official becomes available, I'll post.

Best Regards,

[DonYonce]

Ridiculous ... this is STILL a problem. Autodesk doesn't seem to care.

But, for me, I was able to fix the "Eagle not launching " problem by deleting the libeay32.dll completely.