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.
I can't find anything in terms of logs that indicate what happened. I was able to locate the designer log files and temp directory, but the log only contained the above listed error. I also checked "Event Viewer", since the plugins run in their own process I thought there might be something there.
I'm fairly certain it's a simple missed step or some other issue, but I am having issues debugging. I originally had built the plugin in the WSL (Ubuntu 20.04) and saw another post about the shiv crossing platforms, so I moved it back to Windows 10 and rebuilt the environment, but no luck.
Steps to Recreate
Created an environment: conda create -n alteryx python=3.8.5
Upgrade pip: python -m pip install --upgrade pip
Initialize the workspace: ayx_plugin_cli sdk-workspace-init
Create the plugin: ayx_plugin_cli create-ayx-plugin (chose: single-input-single-output)
Tested the UI
Installed requirements: npm install
Ran the test harness: npm run start
Tested in the harness
Created the Python Environment
Created the virtual environment: python -m venv venv --prompt "alteryx plugins"
Upgraded pip for the venv: python -m pip install --upgrade pip
Installed the "third party" requirements: pip install -r requirements-thirdparty.txt
Verified packages were found through the ide (VSCode)
Installed the plugin: ayx_plugin_cli designer-install --install-type user
Ran Alteryx Designer
Created a new workflow
Configured the workflow to use AMP in the "Runtime" tab
Added an input (simple "csv")
Added the plug-in
Added an output (simple "csv" out)
Ran the workflow
Error occurred: SDK internal error: SDK Tool failed to start
(note: I tried running designer in both standard and "elevated" mode in Windows)
as you didn't provide any part of your source code, it is hard to say what exactly could be the reason. As the error message you mentioned comes from very beginning of the tool lifecycle, I would suggest to check basic things. Eg. whether your
"tool_class_name" in ayx_workspace.json corresponds to your plugin backend class name.