This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
In my Output tool, I have selected "Overwrite Sheet" (problem same for "Create Sheet") and the option to replace the full path by a field:
When I run the workflow, I sometimes get the error
Output Data (20) Unable to make final write to Z:\...\Tables_BRA_Unrelated_Main.xlsx, Error Win32 Error 1175
The error occurs randomly. It's always a different file/sheet Alteryx is trying to write and it occurs only sometimes. I cannot see a logic to when the error is occurring and writing up a toy example won't show you the error message. Z: is a network Windows-share, but the problem also occurs when writing locally.
Previous posts on this error have either used different Outputs writing to the same file (not the case here, just one Output tool), recommended to use a Block Until Done tool (already included, but rather useless anyway if I understand correctly how the tool works), or that an update solves the problem. My Alteryx Designer is already at the latest version 2018.4.
Since there is a lot of data involved in this project and the workflow takes quite some time to run, it is really annoying if it fails at the last minute.
Any idea how to solve this issue? Or is this a yet unreported bug?
Is the data in your output ordered by filename/sheetname? What you're experiencing could be caused by Alteryx opening file A, writing to it, closing it and then repeating the process with file B and then coming back to file A before the OS has had time to actually close it. From what I can see of your workflow, the last sort is by country, etc. Making sure that your top level order is by file/sheetname should remove this problem.
@danilang, Good idea! I moved the Sort tool behind the Formula tool and added the filename as the first item in the list of variables to sort by. For writing to a local drive, this seems to have resolved the issue. When writing to a network share, it's still happening.
So, if I understand correctly, this is indeed an issue of Alteryx trying to write to a file that is still locked by the writer module. Any other way to circumvent this and making sure Alteryx is internally waiting for the file/sheet to be closed correctly?
One thing you could look at is moving the writing component to a batch macro, passing in the list of file names as the control parameter. Within the macro, use a filter tool that's linked to control parameter. It's my understanding(I may be wrong but hopefully someone can correct me) that a batch macro actually waits for file handles to be released before looping. Of course, with this method you'll need a file name field and it will be slower than the in-line method because of the batch overhead. But if it works...
I chanced upon this thread and believe I have the same problem (refer to screenshot). This error occurs rather randomly, the sheet names are not sorted as well - do you have any advice on this? Thanks!