Out Alteryx server has been having an issue and nothing is able to run and not even basic flows on the server.
error we are getting
'Could not init plugin OSError(22, 'The requested operation could not be completed due to a file system limitation')
does anyone have any idea what this error is about?
I republished a single node SF and it fails. here is what I'm seeing when it comes to using the sharepoint and sf tools
works on personal desktop
works on server designer
fails on server
we are all on the same alteryx version, and the tools are are the same version
I tried creating the flow on the server designer, but I got the same results as above
I completely redid my DCM connections for SF, same results
I uninstalled and reinstalled the SF tool on the server for all users, same results
I tried running a text file, and it runs fine
I tried running our oracle connection (uses DCM) and it worked fine
I tried running our BQ connector (uses json key) and it worked fine
as for the run as credentials, we had those as the default, but I'll see if that is something we can test
I`m running out of ideas 😅 One quick test is to add your user (the one you logged onto the server) to the AlteryxService on the Services page and see how that goes.
Best,
Fernando
I'll give that a shot and see how it goes. I know, this is something I have never seen before.
@Blewis21 as noted by @KGT --- this sounds like a python issue.
can you check if python is on your system (ie run python --version or py3 --version in your terminal) --- basically if we can identify is it that Alteryx's python is busted --- or overall python... - also hypothetically you had alteryx 2024.X or 2025.X and then downgraded to 2023.X or 2022.X this would make sense. Alteryx didn't fully uninstall Python 3.10 and you now have to manually clean it up.
my underlying hunch is that your IT has locked down python usage/accessing packages on your server and is blocking python execution/network traffic --- the question is how do you prove that that's the issue and how do you work around it. Some of this is up to you --- but that's my hunch.
@apathetichell , he can use the connector on the Server`s designer with no issues. The issue only happens after publishing the workflow back to the Gallery, which could mean a permission issue on the service account or run as credential that prevents the Python code from being executed, I believe.
@Blewis21 , were you able to make it work?
@fmvizcaino --- thanks --- that would tie into the hypothesis I had above (ie admin accounts can execute correctly --- no admin have a company python setting preventing execution)... Having said that --- if BigQuery runs via BQ connector (not ODBC) on Server --- that might point to something else because it's a Python connector. We probably need local machine execution logs.
perhaps -->
and then seeing if there are additional granular logs?