This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
on 09-02-202101:31 PM - edited on 09-02-202101:31 PM by MatthewP
How To: Perform a Health Check of the Jupyter Environment
This article will review how to perform a health check of the Jupyter environment to aid in troubleshooting issues with the Python Tool. This will help to ensure that Jupyter Notebooks function correctly on the machine outside of Designer.
Procedure to Perform Health Check
Locate the Scripts Folder
Check your version of Designer (Help>About)
For versions 2020.4 and older, go to C:\Program Files\Alteryx\bin\Miniconda3\envs\JupyterTools_vEnv\Scripts
For versions 2021.1 and newer, go to C:\Program Files\Alteryx\bin\Miniconda3\envs\DesignerBaseTools_vEnv\Scripts
Confirm that the Scripts folder contains the files jupyter.exe and jupyter-notebook.exe.
Open Command Prompt
Navigate to the Scripts directory
For versions 2020.4 and older, run the command cd C:\Program Files\Alteryx\bin\Miniconda3\envs\JupyterTools_vEnv\Scripts
For versions 2021.1 and newer, run cd C:\Program Files\Alteryx\bin\Miniconda3\envs\DesignerBaseTools_vEnv\Scripts
How to Interpret Results of a Health Check
If, after running jupyter-notebook.exe, your default browser opens up and shows a blank jupyter notebook, then your jupyter environment is healthy and you can move on to other troubleshooting steps.
If you are missing either jupyter.exe or jupyter-notebook.exe, then you have an unhealthy installation. Contact Support to get a copy of the missing file. Then, perform the health check again.
If you have both files but running jupyter-notebook.exe results in errors within Command Prompt, then you are most likely missing some dependencies and have an unhealthy environment. Save the error messages you receive and contact Support.
There’s an exception to every rule, isn’t there? In this case, it is actually possible that this Health Check could produce errors in Command Prompt on a machine that is able to run Jupyter notebooks just fine within Designer. This doesn’t come up much because, well, if it’s working in Designer our users are typically content. However please be aware that we have seen at least one such error:
The error message ModuleNotFoundError: No module named ‘pysqlite2’ indicates that the machine is missing the python package pysqlite2. While this does indicate an unhealthy Jupyter environment, as Jupyter did not open correctly, this machine was able to run Jupyter within Designer just fine.