Unable to open file for write

[Sreenath_001]

I have the workflow created and saved in Alteryx server. When that is executed, sometimes it works and sometimes it triggers error as "Unable to open file for write: Can't open file as the process cannot access the file because it is being used by another process". What's the fix for this. Attached screenshots of success and failure messages of the same workflow ran on different time frames.

[Sreenath_001]

Attempted replacing Parallel Block Until Done tool with simple Block Until Done tool as suggested and still have the same error. Can't alteryx wait until the output file is written to start with next output file? If such errors exist what is the use of this tool? Can someone please explain or help?

[jdminton]

It works in our designer desktop versions, so it’s something else. I’ve had some files gets accessed by things that “checks out” the file and prevents changes. I’m confused by this one because you only are getting 3 errors. You should get 5 if the file is in use before running the workflow. Again though, I only received three errors when I removed all block until done, so it’s acting like your tool doesn’t work. It was also interesting that the cleanse tool didn’t work when you brought in that other workflow. 

if you put containers around the each of the outputs and turn off the two largest, do you get any errors?

[Sreenath_001]

Hi, Out of 5 container output tabs, I turned off the containers of 2 outputs that has around 15k line items in each. The rest 3 containers have 2 summarized pivot outputs and one container output has only 38 line items. And here is the result when ran.

[jdminton]

Can you try renaming the results.xlsx file to -old and try running again? If it’s an Excel corruption issue, that should eliminate that. If it still doesn’t work, 

[Sreenath_001]

As suggested I have renamed my file from Result.xlsx to Result1.xlsx. However, there is no change in the error status.

[jdminton]

This is very strange. Have you restarted your computer recently? I don’t think it’s likely to change anything, but it may. With Alteryx not able to access cleanse.yxmc earlier, I’m wondering if it’s having trouble using block until done. It acts like block until done isn’t working. Since it’s working fine on other machines, you might want to reinstall if the restart doesn’t help. If that doesn’t work, I’d put in a support ticket as this doesn’t seem to be a workflow design issue. I wish I could help more.

[Sreenath_001]

Yes I restarted my system recently. There is another project going on from an year and that also have the same issue. Because of this error, it prolonged for an year as I was busy constantly looking for alternate ways to get that completed using Alteryx itself but the tool failed me. Finally I managed to complete it using excel scripts dumping Alteryx. I had liaised with Alteryx IT support as well regarding this issue but they were not of any help. I checked with colleagues who use Alteryx and they don't face any similar issue eventhough they use Bloc Until Done tools in their workflows. Do you think a reinstallation of Alteryx designer would help to settle this? Please advise. 

[jdminton]

I can't be certain since I don't have the same issue, but I would definitely reinstall. Make sure you use the default settings on the reinstall. If you put it in custom locations, that may cause some of the problems you are having. I can think of no other reason for you to experience these issues. I hope it works!

[jdminton]

I experienced the same issue with block until done on a separate workflow that I created. I'm not sure how it would happen only on a created workflow, but Alteryx support ran my non-working workflow fine. I was able to get it working by removing 1 block until done tool. @Sreenath_001 , can you try removing one of the block until done tools and see if your workflow works correctly? Thanks!

Edit: my workflow also runs fine when turning off the amp engine.

[Sreenath_001]

I simply created a folder and saved output file in it. The workflow ran successfully and so far there is no error generated.