Closed 1kastner closed 10 months ago
The text in the window roughly translated to:
Procedure entry point could not be located for pythoncom38.dll
The entry point is ?init@PyWinBufferView@@QEAA_NPEAU_object@@_N1@Z
The path to the pythoncom38.dll file should be self-explanatory.
The popup shows up every maybe 5 minutes while I use JuypterLab. There is no link between me running any code and the popup. It even shows up when I am doing something else, e.g. sharing PowerPoint slides. As long as I don't close the popup window, the execution of a cell in a Jupyter Notebook stops. Once I click on "ok", the execution continues. We talk abour arbitrary Python code here, e.g. The output looks as expected, so the error message is rather annoying than helpful.
This sporadically appearing error message continued to show up even after I removed my previous Anaconda version and freshly installed the latest one available for download on the official side. Further information on my conda environment can be found at https://github.com/1kastner/ml-potentials-and-risks, the environment is described in https://github.com/1kastner/ml-potentials-and-risks/blob/master/environment.yml.
I set up another conda environment with a different set of libraries and the general issue persisted.
I face the same issue with python 3.9 with exactly the same error message on my two machines with the same environment. A downgrade to 3.8 fixed the issue for me. I read somewhere that this can occur if you have different patch versions of python installed in the environments, because the pythoncom*.dll is shared between the environments. But if I force all my environments to 3.9.7 the issue still occurs.
Thanks for the hint, @sven5s. Do you have a source where the patch issue is better described? Additionally I found https://stackoverflow.com/questions/68925724/anaconda-environment-error-procedure-entry-point-could-not-be-located-for-pyth and the error message looks very similar. Also I use nb_conda_kernels in my environment. Are they indirectly the culprit? I dont want to download a dll file from a third-party webpage (as suggested on stackoverflow) so I tried to copy trick. However, my W10 didn't allow me to overwrite the pythoncom38.dll file for some unspecified reason.
I deleted the dll and for now everything seems running peacefully. A weird behavior indeed.
I found the same link and also this two. Maybe my conclusion was not correct but it was the right direction.
I solved my issue. The problem was that miniconda used python from anaconda repo and my jupyter environment used the conda-forge repo. Now the activation of the jupyter environment was not working correctly in the cmd and so also in my self created shortcut. I could run the jupyter exectuable but the pythoncom*.dll from the base environment was used. Now I use conda run and everything works.
Well, they seem related (definitely right direction) but not exactly the same. So thanks again! However, I hope this issue can be solved professionally so that the next user doesn't need to go through this.
Hi there. Having the same issue after updating my Anaconda to
conda version : 4.11.0
conda-build version : 3.21.4
python version : 3.8.8.final.0
This error message pop-up as a Windows error message, exactly as @1kastner posted. Tried to reinstall or replace the dll file but with no avail. thanks!
As described in https://github.com/conda/conda/issues/10926#issuecomment-928974593, by deleting the file it was solved. Currently I just rename the pythoncom38.dll to pythoncom38.dll.bak (just in case) and afterwards the pop-ups immediately stop.
This does not work for me. The warning from Anaconda Prompt is gone, but I have again the same as soon as I open any Jupyter Notebook.
I can confirm I renamed the pythoncom38.dll to a _bk version.
edit: actually removing the .dll file make it worse, since the popup appear everytime I refresh the kernel; otherwise, leaving "as is" it "just" appears launching JN from Anaconda Prompt.
Just for info, I'm having the same issue now that I upgraded the Python version to 3.10 from 3.9.
Quick update, my problem seem to have disappeared.
My actions:
ipython kernel install --user --name=<any_name_for_kernel>
from the new environment.Once I removed the old environment, Jupyter Lab complained about the lack of kernel, so I had to reinstall it, but this seems to have worked fine.
Ran into the same issue after running conda update --all
Removing the corresponding library solved the issue:
I have the suspicion that the offending library originates from previous Python versions installed/uninstalled by the official Windows installers.
Hi there, thank you for your contribution!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.
If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment.
Thanks!
Checklist
What happened?
From time to time, this popup window appears. Everything else seems to work but the popup window is worrisome.
Conda info
Conda config
Conda list
Additional Context
No response