InboundNamedPipe GetOverlappedResult: The pipe has ended ERROR

[hellyars]

My workflow is generating the following error:

InboundNamedPipe GetOverlappedResult: The pipe has ended

The error DOES occur if I have Enable Performance Profiling selected.  The workflow fails in 1.6 seconds - seemingly before it completes reading the XML input files.

The error DOES NOT occur if Use AMP Engine is selected (only).  The workflow completes in 18 seconds.

The error DOES NOT occur if I run the workflow without AMP Engine selected.  The workflow completes in 30 seconds.

No more Mac.  This is running on a Windows 10 PC, 16-core, 64GB RAM, 2TB NVMe SSD with up to 40GB of RAM allocated to Alteryx.  There is no 3rd party anti-virus software installed --- learned my lesson after MalewareBytes attacked Alteryx.

[danilang]

Hi @hellyars 

As @CharlieS, so eloquently stated here, 

In my experience, the "Error: InboundNamedPipe GetOverlappedResult: The pipe has been ended" error is one of the non-descript errors that comes up in a number of situations when another, more specific error message isn't available.  

If you check the recommendations that are linked to the right of your original , you'll find this error thrown in multiple unrelated scenarios.  

I've tried using the 4 combinations of AMP/Profiling using various XML files and can't recreate your error. Can you provide a minimal sample workflow and input data where this occurs.

Dan