file system limitation

Blewis21

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?

Error Message

Server

Accepted answers

All comments

fmvizcaino

Hi @Blewis21 ,

I have never seen this error before, but since you can`t run any workflow, I would check the disk space where your Alteryx Server is installed and the workspace configured to create the temp folders.

Here you can see how to find your workspace path. https://knowledge.alteryx.com/index/s/article/How-To-Safely-change-the-Global-Workspace-of-an-Alteryx-Server-1583461568261

Another problem could be permission issues. You can look at your Windows events and see if you can find this error. You may find more clues to what is happening. https://knowledge.alteryx.com/index/s/article/How-to-Retrieve-System-and-Application-Logs-for-Alteryx

Best,

Fernando Vizcaino

KGT

Yep, I second the response by @fmvizcaino, first look to see if the disk drive on the server has any issues (space/location etc). It could also be the user that the server is running as pointing it's temp files to a Onedrive/Dropbox etc location and that causing issues.

Other reasons for this may be invalid characters in file paths and things like that, but I would think that would be workflow dependent unless you have your Server Settings pointing to a weirdly named directory or a cloud fileshare.

Blewis21

Hey everyone,

I want to make a correction here, as we found a common issue.

it appears to only happen when we have some sort of data connection. (salesforce and sharepoint are the ones we use)

storage: 400 gb with 130gb free

memory: 200 gb

fmvizcaino

Hi @Blewis21 ,

Was this working before? Have you gone through a server upgrade recently?

Firstly, check if the connector is working on your Server. Open the Server Designer (available on the server where Alteryx Server is installed) and test the connector there.

Secondly, it may be a version mismatch. I would check the connectors installed on the Server vs the connector used by the user who published the workflow to the server. In this link, you can find where the connectors are located. https://help.alteryx.com/current/en/designer/tools/connectors.html#connectors

Best,

Fernando

Blewis21

thanks for the info so far.

I've checked the work file path and it's the default ProgramData/Alteryx/

this was working but we had to move from a 32 core to a 4 core system due to our contract change and it seems to have broken once we moved.

I was thinking maybe it's because we were only on 4 cores, but a 4 core should be able to handle a very basic SF pull.

I'm going to delete the connecotrs and reinstall them and see if that fixes it.

Blewis21

reinstalling the connectors did not solve the issue

Blewis21

I went into the server, got into the designer there, pulled the flows that are failing, and ran them and the work fine inside the designer in the server.

fmvizcaino

4 cores is fine, I don`t think that alone could cause this issue.

Could you try republishing the workflow to the Gallery? Sometimes when you open the workflow on Designer, the tool configuration gets adjusted automatically.

Here is another idea: Do you have a run as credential or service account configured for your server? If you do, you can log into the server with that account and test the workflow with that account as well.

KGT

Something of note here is that they are both Python based connectors and searching for Iso of that error on SO has a lot of Python responses.

Some possible items:

Path lengths longer than 260 characters
Unable to install a python package, due to permissions that the workflow is run with (Check Run-As user)
Mismatch of connector to version. (Most commonly this would be after an upgrade of Server though).

Blewis21

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

fmvizcaino

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

Blewis21

I'll give that a shot and see how it goes. I know, this is something I have never seen before.

apathetichell

@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.

fmvizcaino

@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?

apathetichell

@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 -->

https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Discussions/Enabling-logging-through-command-line/td-p/85499

and then seeing if there are additional granular logs?

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703