Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

JupyterFlow DLL Load failed in zmq\backend\cython

JeffA
Alteryx Alumni (Retired)

Originally posted by @jrgo here

 

When running JupyterFlow from Designer, everything works. But when running it from Server, I get this error:

 

  File "C:\Users\service-account\.shiv\99b9e8838bc10d0-cv-0-1_e20b05ea24484f9870ce408477e8f9e6c142d0c976ea8c102877ed12647d4512\site-packages\zmq\backend\cython\__init__.py", line 6, in <module>

    from . import (

ImportError: DLL load failed while importing error: The specified module could not be found.

This prevents JupyterFlow from working when running on Server.

Jeff Arnold
Sr. Full Stack Software Engineer | Alteryx
2 REPLIES 2
JeffA
Alteryx Alumni (Retired)

This issue is caused by a vcruntime140_1, a .dll file that is normally present in the user's system32\ directory, being missing. For many users, that .dll is not missing, but for some reason it's not there for others.

 

The solution is to install the latest version of the JupyterFlow yxi (version 0.2), as the .dll has been added as a dependency in that. To find the latest version of JupyterFlow, check out this article.

 

If version 0.2 is not available yet, it should be posted by 24 September, 2021.

Jeff Arnold
Sr. Full Stack Software Engineer | Alteryx
evanmirk
5 - Atom

To make it short, it means that you lacked some "dependencies" for the libraries you wanted to use. This is a common problem when installing python packages, mainly in windows. Before trying to use any kind of library, first it is suggested to look up whether it needs another library in python "family".

 

The solution is to provide the python interpreter with the path-to-your-module/library. The simplest solution is to append that python path to your sys.path list. In your notebook, first try:

 

import sys
sys.path.append('my/path/to/module/folder')

 

This isn't a permanent change in sys.path, because when you log out, your environment is reset, so any variables you may have set are lost.

 

The better (and more permanent) way to solve this is to set your PYTHONPATH, which provides the interpreter with additional directories look in for python packages/modules.

 

from BASH type: export PYTHONPATH=/path/to/new/folder:/another/path/...../ #each path must be separated by a colon

 

Labels