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?

[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-Altery...

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

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