Output Tool error when writing a Hyper file to a local drive

[mkosmicki1]

Hello Maveryx! I have some workflows that use an output tool to create a local Tableau hyper file. On Monday, I started seeing the following error:

Error: Output Data (51): Failed to start a new Hyper instance.

Context: 0x86a93465

Caused by:

The Hyper server process exited during startup with exit code: -1073741818

Command-line: ""C:\Program Files\Alteryx\bin\Tableau\bin\hyper\hyperd.exe" "run" "--date-style=MDY" "--date-style-lenient=false" "--init-user=tableau_internal_user" "--language=en_US" "--log-config=file,json,all,hyperd,0" "--log-dir=C:\Users\MKOSMI~1\AppData\Local\Temp\Engine_4368_9758cae846394b439abd513fda1362c1_" "--no-password=true" "--skip-license=true" "--listen-connection" "tab.pipe://./pipe/auto" "--callback-connection" "tab.pipe://./pipe/{08C875ED-00E4-45AF-8BAB-DAE2BE753BA5}" "

Context: 0x13cead20

The error occurred in established workflows. I tested using a fresh tool in a new workflow...same error.

I searched for the error in the community and on google...and couldn't find anything other than it might possibly be an anti-virus issue? (if all else fails blame the anti-virus program LOL)

Anyway, I'm guessing this is likely something to do with python and the Tableau API...but I'm not entirely sure how to correct it, other than writing files to another format and creating the Hyper File extract via Tableau.

Anyone else seeing this? Possible resolutions?

[mkosmicki1]

Upgrading to 2023.2.1.7 seems to have resolved the issue. However, it only occurred in my alteryx version and not in my co-workers versions. So I'm not sure it was a bug or my computer.

[jarc1978]

"Hi mkosmicki1, I just had the same problem. I discovered that the issue is we need to give write permission to the hyperd.log file that is created in the same root where the workflow is created.  I hope this can help someone else in case they encounter this problem when trying to save a hyper file. By the way, this only happens to us with version Tableau_v1.4.0 since I don't see previous versions generating this log file.

[DavidP]

Hi @jarc1978 - you just saved me a bunch of time! Thank you.

When reading your response, I realsed that I had opened and"autosave" version of my workflow. Autosaved workflows are save in a place on the drive where my runAs user account doesn't have write permissions. So when I saved the workflow in my Documents folder, it ran without issues.

Thanks again.