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.
We thought about bypassing the JIT Debugger Exception thrown by Windows Server 2012 R2 by deleting the registry keys for the JIT Debugger, however, we didn't go through with this because it sounds like a bad idea.
So, as of now, it is blocking our production Alteryx 11.0 servers ability to utilize the Conditional Runner and other Crew Macros that rely on AlteryxRunner.exe.
1. What version of the Crew Macros are you using? Crew Macro Pack - 2016 Q2 Release
2. What version of Alteryx? Server 11.0
3. What version of Windows? Windows Server 2012 R2
4. 32-bit or 64-bit Alteryx? 64
5. Have the runner macros ever worked on the affected machines? No
I'm also having a similar issue. My first runner properly executes the first workflow, however, it stops and does not run the next workflow due to "errors." There are no red errors, but there are some conversion errors (that don't corrupt the file). I cannot figure out how to get this to properly run and any advice would be greatly appreciated.
I am also having a similar problem. I have a list of workflows scheduled on the server, using the list-runner. I am currently using Version 1.0 of the List-runner. Further, I am also publishing to Tableau Server using the Publish to Tableau Server macro.
The weird thing is that it worked some weeks ago, but now it seems as a problem arises. I keep getting an error in the output-log similar to yours:
Designer x64 Tool #4: Tool #3: Iteration #1: Tool #5: Record #1: Tool #2: Tool #2: The external program "SupportingExes\AlteryxRunner.exe" returned an error code: -1073741818
Designer x64 Tool #4: Tool #3: The output connection "Logs" was not valid
Do people have any idea about the reason for this?
I'm not sure if this helps but I encountered a similar error on a Windows Server box when I was using a scheduled workflow with a different "Run As" user than who installed the CReW Macros. Once I gave the "Run As" user access to the drive with the CReW Macros I avoided the error.
Just found this. The solution for me was to include the location of the AlteryxEngine.exe in the path of system variables on the computer. Basically the error message is saying I can't find the Alteryx exe, and that it needs to be added to the variables on that windows maching