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.
I also have encountered this error. See attached screenshots. Since the error mentioned "Designer" I tried also running the workflow from the command line using AlteryxEngineCmd.exe. In that case the job simply crashes with no useful error message. It did seem to crash at the same place according to log output. I really need to resolve this and the error doesn't provide any useful clues. Alteryx, how can I debug this? I have confirmed plenty of physical memory and disk space.
Following up on my earlier post. I was able to track this down to a currupt yxdb being read. I had copied the yxdb files from another networked server. The file sizes were the same but apparently the files were not exactly the same. Recopying the yxdb file fixed this InboundNamedPipe error upon rerun.
This is a common error that is typically thrown for unknown reasons. Sometimes it is due to a corrupt file as mentioned above, but normally it occurs because of an unaccounted for reason. Other users have reported changing a Union tool from Manual Configuration to Auto has resolved the issue as well. When you get this error, it is best to reach out to your Client Services Rep who will work with you directly to try to reproduce and fix your issue, or so it can be escalated through the proper channels.
Came across this error when outputing a file to 1) YXDB and 2) SAS format simultaneously (2 separate outputs). The SAS file did not get generated, so likely an issue with writing the yxdb. I went into the output tool and ensured the output file name included the .yxdb extension and it seemed to resolve.