Error in writing output from gallery to server

[ashiques]

Hi All,

I created an app which take input from local folder and write the output in same local folder in a different file.

This folder is sync with box app. So when ever I update the Box file from browser it automatically update my local files.

When upload the app in alteryx gallery it takes the input correctly but giving error in writing the output in file. below is the image of that.

For input from it gives me error for "Path not found" but in the ouput it gives me error of "Cannot access the folder".

Is this because alteryx server is in different location or the box folder which is present in server locally is accessible to the credential of its owner or something else.

[JordanB]

Hi @ashiques,

Are you developing this workflow locally or on the server?

If you are doing this locally you will need to check the following:

1) The server can see the folder. From first inspection it looks like you are pointing to  a mapped drive 'F'. The server may use a different mapped value, so what you can do is replace the mapped value with the server name where that folder resides. This should be bale to give the alteryx server visability to it.

2) You may also need to check the 'Run As' user for the alteryx server has access to that folder aswell.

If you are devloping on the server you can check the following:

1) You may also need to check the 'Run As' user for the alteryx server has access to that folder aswell.

Best,

Jordan Barker

Solutions Consultant

[ashiques]

Hi @JordanB,

I am developing it locally and then upload it on gallery. I didn't test it directly on server.

I am able to take the Input from the server path F:\AR_analytics_box_sync\Box Sync\AR Analytics

But when I try to write the output it gave error of Cannot access the folder. It give error in designer itself before uploading it in the gallery. Output path is F:\AR_analytics_box_sync\Box Sync\AR Analytics\APP_Outputs\abc Report.xlsx

In the Input it says unable to find the file but in the output it says cannot access the folder. I don't think it is the error of map drive because we are able to get the input from same path. I think it is because of access permissions on the APP_Outputs\abc Report.xlsx am I correct or not.

Also pls let me know what is this "RUN AS" I don't understand it.

Thanks

[JordanB]

Hi @ashiques

Yes access is most likely the issue then! 

The 'Run As' account can be set up on the Alteryx Server. This relates to the credentials (Username/password) which the scheduled/workflows are ran under, meaning whatever credentials that Run As has, this will influence the permissions of the workflow. 

If no 'Run As' has been set (This is an option, it can run as local service account), then I would check with your Alteryx server admin to check the permissions to the folder.

Best,

Jordan Barker

Solutions Consultant 

[ashiques]

Hi @JordanB

I am able to run this module from server and able to write the output file.

But at the same time when I upload it in alteryx gallery I am not able to create the output. It results as Not output generated.

[JordanB]

Hi @ashiques

If you are looking at the writing to that location please see this article

As default when you upload to Alteryx gallery it will put the output in an externals folder. Using the article above will show you how to rite to a specific location.

Best,

Jordan Barker

Solutions Consultant

[ashiques]

Hi @JordanB I already done that.

I query on that my Alteryx gallery and alteryx server will have the same file path. Because gallery is running on that server only.

[JordanB]

Hi @ashiques

Can you leave the output file ticked in the workflow assets. This should then allow you to see the file output in the gallery.

Best,

Jordan

[ashiques]

I have done that but still get the error. Cannot access the folder. Should I use this https://community.alteryx.com/t5/Alteryx-Knowledge-Base/Adding-Files-to-the-Gallery/ta-p/17096 to setup the output path.

[Niekka]

One thing you could confirm, is that the paths to the output file are abolute and not relavtive when you upload, this could otherwise create this issue.