Problem
I created a basic plugin following the "Platform SDK Quickstart Guide" and the "ayx_python_sdk documentation". After performing a ayx_plugin_cli designer-installand creating/executing a simple workflow the new plugin is throwing an error:
SDK internal error: SDK Tool failed to start
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
(note: I tried running designer in both standard and "elevated" mode in Windows)
Detailed Information
OS | Windows 10 Pro (20H2) |
Miniconda | 4.10.3 |
Python | 3.8.5 (Conda Managed) |
Node | 14.17.4 |
Alteryx CLI | 1.0.0 |
Powershell | 7.1.3 (core) |
Alteryx Designer | 2021.2.1.35394 |
Python Packages | python_pip_freeze.txt (attached) |
Node Packages | npm-packages.txt (attached) |
Logs | (attached) |
Hi @wbellman ,
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.
Hello PetrT!
I am providing source, however the steps to duplicate listed above, reproduce the error "out of the box" and requires no custom code at all, at least on my system.
I've attached the generated file structure from the steps listed above (see: test-plugin.zip). I have not made any changes except for the custom inputs listed above and using the name "SimplePlugin".
My suspicion is that it is environmental not code, but that's just a guess... and also the reason I included the setup for the environment and the OS details.
Please let me know if you need further information.