Alteryx Server Knowledge Base

Definitive answers from Server experts.

Error: NoSuchKernel: No such kernel named designerbasetools_venv

d_vansell
Alteryx
Alteryx
Created

Error: "No Such kernel named designerbasetools_venv"

If the Server was upgraded from any version 2021.1 and older to a version of 2021.2 or greater, then the workflows published to the Gallery with the Python tool will throw this error "NoSuchKernel(kernel_name) jupyter_client.kernelspec.NoSuchKernel: No such kernel named designerbasetools_venv ".


Prerequisites
  • Server
    • 2021.1.1 and Newer
    • Python tool in the workflow
NoSuchKernel(kernel_name) jupyter_client.kernelspec.NoSuchKernel: No such kernel named designerbasetools_venv
  • When you run the workflow from the Gallery, it throws the above error. However, if you open it locally and run it, it works fine.
  • When you try to save a workflow to the gallery and get a traceback error message during validation
  • When you try to save a workflow to the Gallery and has errored during validation
image.png
 

Cause

The cause of this is that when the upgrade process happens, the kernel folder and display name still reference the older Python3 or jupytertool_venv kernel name instead of the new designerbasetools_venv name. 

 

Resolution

First, Try running Designer on the Server machine.   This should automatically make the name change.   If the error persists, please continue to the following steps:


 The following should be done on all worker nodes in a multi-node Server environment.

  1. To resolve this issue, make sure that all instances of Designer on the Server are closed.
  2. Open a File Explorer and navigate to the following location:  %Installed_Location%\Alteryx\bin\Miniconda3\envs\DesignerBaseTools_vEnv\share\jupyter\kernels
  3. The folder may be named "python3", "PythonTool_vEnv", or "JupyterTool_vEnv" (depending on what you upgraded from). Rename the folder you find to "DesignerBaseTools_venv."  If you see more than one folder, remove the older "python3" or "PythonTool_vEnv", and rename the "JupyterTool_vEnv".
  4. After that, double click that folder and local the kernel.json
  5. Open the JSON in any text editor
  6. For the line "display name," change "python3//JupyterTool_venv" to "DesignerBaseTools_venv" and save the file
  7. After this, reopen Designer and the workflow throwing the error earlier, and run it. Once you confirm it works through Designer, try to run it from the Gallery again or upload it to the Gallery again.


Additional Resources

No ratings