How to Fix Entry Point Not Found while installing libraries in conda environment

Question

I\'m working on anaconda by making multiple environments in it. I have made any environment camelot so now I want to install in different libraries in this envi

Answer 1

As mentioned by an Anaconda maintainer here ...

moving libssl dlls around like that is really not advisable. Those DLLs are duplicated because you have something fishy going on in your packages. There should not be any openssl DLLs in the DLLs folder. They should be in Library/bin

By looking at the JSON files in the conda-meta directory I found out that DLLs\libssl-1_1-x64.dll was installed by the python 3.7.0 package, and Library\bin\libssl-1_1-x64.dll was installed by the openssl package. After further investigation I found out that Python 3.7.0 does not install OpenSSL as a separate package, but Python 3.7.1 (and later) does.

Typically upgrading Python goes as expected, but if you somehow end up with both python 3.7.0 and openssl packages installed simultaneously there will be two libssl-1_1-x64.dll files and your Anaconda distribution will be broken. (You can easily verify this with the conda list command.)

I think the best way to fix it is therefore:

1. Rename Library\bin\libssl-1_1-x64.dll to Library\bin\libssl-1_1-x64.dll.org (your are going to need it later.)

2. Copy DLLs\libssl-1_1-x64.dll to Library\bin\libssl-1_1-x64.dll

3. Update Python to version 3.7.1 or higher, for instance with conda update python. This will remove the DLLs\libssl-1_1-x64.dll file.

4. Delete the current Library\bin\libssl-1_1-x64.dll file.

5. Rename Library\bin\libssl-1_1-x64.dll.org back to Library\bin\libssl-1_1-x64.dll. This is necessary because I got HTTP errors in the next step otherwise.

6. Reinstall OpenSSL with conda install openssl --force-reinstall to ensure it's up to date again.

Answer 2

I was receiving the same following error while updating spyder and conda package.

python.exe-Entry Point Not Found
   The procedure entry point OPENSSL_sk_new_reserve could not be 
   located in the dynamic link library.
   C:\Users\abc\Anaconda3\Library\bin\libssl11_-x64.dll

solution:

• I did replace libssl-1_1-x64 dlls from Anaconda/DLLs to Anaconda/Library/bins as suggested here.
• Before opening Anaconda Navigator desktop app, I updated conda in Anaconda Prompt using conda update conda. conda successfully updated.
• Then I have updated spyder using conda update spyder command in Anaconda Prompt. spyder updated and running successfully.

Answer 3

My problem was same. I just uninstalled anaconda, and install it again. And the problem solved.

Answer 4

I got the same issue while updating Anaconda navigator, and got it over by replacing the file libssl-1_1-x64.dll in Anaconda3/Library/bin with the one from Anaconda3/DLLs.

Answer 5

For those still having similar issues with libssl11_-x64.dll or other .dll files:

Use pip install instead if you can!

---

I had the same issue today with libcrypto-1_1-x64.dll when trying to install plotly using

conda install -c plotly plotly

This prompts a downgrade for anaconda, and in turn raises the error:

OPENSSL_sk_new_reserve [...] libcrypto-1_1-x64.dll

Instead, using for example

pip install plotly==4.1.0

works like a charm!

Answer 6

I had the exact same issue, and it also just started today. Kind of destroyed my entire work day, tbh...

I accidentally did a conda install ... in my base environment, and it updated conda and a handful of other modules. (Conda went from 4.5.12 to 4.7.10, in my case.) Anyway, after I rolled it back, things are working as expected again.

If this is what's causing your issue, here's a fix.

1. conda list --revisions

2. conda install --revision 1 (In my case "rev 1" was my most recent, stable base environment.)

(More details about this: https://sriramjaju.github.io/2018-05-30-2-minute-recipe-how-to-rollback-your-conda-environment/)

Now I'm worried that I've inadvertently configured something in a way that isn't compatible with the newest version of conda.

Edit: Don't follow this last suggestion if you're doing anything other than playing around in a conda environment to test-drive modules. See this and this.

Lastly, if you really need to install modules and do some work ASAP, pip install [module name] was still working for me before I thought to do the reversion thing.