Alteryx Designer Desktop Knowledge Base

Definitive answers from Designer Desktop experts.

AlteryxRPluginEngine.dll could not be loaded

DaveF
Alteryx Alumni (Retired)
Created

AlteryxRPluginEngine.dll could not be loaded: The specified procedure could not be found

 

When running any of the R-based predictive tools in Designer, you may come across the below error message:

 

AlteryxRPluginEngine.dll could not be loaded: The specified procedure could not be found. (127)
DaveF_0-1573591363092.png

 

Environment

 

  • Product - Alteryx Predictive Tools
    • Any R-based predictive tool (Linear Regression, Decision Tree, Association Analysis, etc.)

Cause

 

Typically this error is caused by having a mismatch in versions between Designer and Predictive Tools. It is required that both Designer and Predictive Tools are on the same version number (e..g, 2018.4) and type (Admin/Non-Admin).

 

Solution

 

  1. Search Windows for "Add or Remove Programs" or go there through the Control Panel
  2. Uninstall both Alteryx Designer and Alteryx Predictive Tools
    • Note 1 : If the Alteryx installation is an Alteryx Server, please uninstall the Predictive tool installation alone and install the matching Predictive tool version, as uninstalling the Designer alone on an Alteryx Server based environment, will cause multiple issues.
    • Note 2: If Alteryx Designer is a standalone instance(i.e - only Designer is installed, and no Alteryx Server is installed), it is fine to only uninstall either all Admin versions(both Designer and Predictive tools), or all Non-Admin versions, if desired. Non-Admin versions will say (User) in parentheses.
    • DaveF_0-1573591816060.png
  3. Download the matching versions from the Downloads page
    • Admin example: AlteryxInstallx64_2019.3.5.17947.exe ANDRInstaller_2019.3.5.17947.exe
    • Non-Admin example:AlteryxNonAdminInstallx64_2019.3.5.17947.exe ANDRNonAdminInstall_2019.3.5.17947.exe

 

Additional Resources

 



null
Comments
SeanAdams
17 - Castor
17 - Castor

It really is great that you are writing these cases up with the error details so that they become a resource to find when someone faces a confusing red error message that they dont understand.

 

 

This seems like a wonderful way to turn support issues into a re-usable asset that uplifts the entire user base.

Junya_Wang
8 - Asteroid

I found this helpful. Thank you