Alteryx Server Knowledge Base

Definitive answers from Server experts.
How to chain workflows together
View full article
Using AlteryxEngineCmd.exe in the After Run event of a workflow to call another workflow returns "error code: 1: The system could not find the environment option that was entered. (203)" if this workflow completes with warnings.
View full article
Logs and files can be hard to find if you’ve never had to deal with them before. This Alteryx Analytic Application will help gather most of the common logs and environmental files Support requests in one fell swoop!
View full article
How to schedule a workflow using Event Run Command
View full article
If you have written an external script to use a COM object, for example, Microsoft Excel and the workflow uses this, you will need to ensure that the appropriate permissions have been given to the group of users or specific users in order to run the script successfully on the Alteryx server. This article guides you through the steps needed.
View full article
Issue   The run command from either the event or the tool used to run an external script (VBScript) that contains the code to access the Excel object does not execute successfully on Alteryx Server. The job exits with a timeout error.   Error running Event #1: The external program <EXTERNAL_PROGAM> timed out after <TIME> ms   Configuration Example:   Script example:     Option Explicit Dim objExcel Set objExcel = CreateObject("Excel.Application") .. .. objExcel.Application.Quit Set objExcel = Nothing     Environment   Alteryx Server   Diagnosis    To diagnose the actual cause of the issue, add debugging statements in the script to find where the code may be breaking on the server. Suggested code:     Option Explicit Dim objFileToWrite Set objFileToWrite = CreateObject("Scripting.FileSystemObject").OpenTextFile("C:\temp\debug.txt",2,true) objFileToWrite.WriteLine("Starting log") Dim objExcel Set objExcel = CreateObject("Excel.Application") objFileToWrite.WriteLine("After Object Instantiation") .. ..     Solution   The solution will depend on the cause of the issue.   In general, when a COM object is used, do ensure that the account that runs the workflow on the server has the necessary permission to launch and activate the COM object. If the debug statement does not go past the COM instantiation, it is likely that this is a permission issue. In this case, check the Windows System Event log for the actual error. Please refer to the "Additional Resources" section to enable the COM object on the server.     Additional Resources   To enable COM object on the server 
View full article