Error starting Pycharm console, dll load failed

Hi,

When I start Pycharm 2019.3 Python Console fails to start with an

 ImportError: DLL load failed: The specified procedure could not be found.

If I start Pycharm from anaconda prompt the console loads fine. That led me into looking at the paths, and while testing I found a solution that works for me.

Go to Settings -> Python Console and look at the environment variables in the top right corner. Mark the Path variable and copy it, and paste the result into Environment Variables text box. Write anything, like the letter x at the start of the path

This solves it for me. 

 

 

 

6 comments
Comment actions Permalink

Is it a standalone PyCharm installation or through Toolbox App?

What conda version do you use? conda --version command should do the trick

0
Comment actions Permalink

Also, which conda executable did you use to create that environment?

0
Comment actions Permalink

It's a standalone PyCharm installation. conda version is 4.7.12

I don't understand what you mean with which conda executable I used to create the environment - do you mean which conda I had installed when installing PyCharm? I might have installed a new version of Anconda in a different location after the PyCharm installation, but everywhere I look python points to the correct version.

I have read a lot of posts about the same problems. Surely the path "trick" must point to some kind of bug in PyCharm path handling?

0
Comment actions Permalink

When creating a new conda environment in PyCharm, there is a field called Conda executable:

Which one do you use? Could you share a screenshot?

It is indeed a bug in PyCharm, but, unfortunately, we are having no luck in reproducing it. There was a known issue that should be fixed since 2019.1 version https://youtrack.jetbrains.com/issue/PY-27234

0
Comment actions Permalink

Please see attached screenshot. Please note that 

1) I work with existing interpreter and have not created or referred to conda in PyCharm
2) The path to the conda executable is correct in the screenshot
3) The default path to the environment points to a read-only directory where I can't create an environment
4) For me it works after the path-trick.

 

 

Kind Regards

 //Fredrik

0
Comment actions Permalink

Do you have PYTHONPATH defined in the system or some Python-related stuff in the system PATH?

Please file an issue to our issue tracker https://youtrack.jetbrains.com/issues/PY

0

Please sign in to leave a comment.