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.
Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email email@example.com for assistance.
Prescriptive tools with the R logo in the bottom left corner of the icon
If the tool throwing this error is successfully outputting data, and the exit code is not 1, this error can likely be ignored. These are return codes from the Microsoft Visual C++ runtime libraries. R considers any return code other than zero to be an error. Although Microsoft hasn't publicly published definitions for these codes, the R Core team has found that these non-zero errors do not impact outputs and should be ignored.
A true R error that indicates an issue with a line of code will have a return code of 1.
Most of the R.exe exit code (1) errors from our R -based macros come from:
incorrect data types
improperly formatted data
This list is not all-encompassing, as there is no singular cause to this error. Extensive use of the Data Cleanse tool and Data Investigation tools will help lessen the possibility of errors for both new and advanced users. First, more information on what is happening is available by clicking the Show All Macro Messages option in your Workflow - Configuration, Runtime tab. This will enable more information to come through in the Results window. There are often clues in this text coming directly from R that can help you troubleshoot the error (in the second image).
Note: In the Optimization tool, the solver in R requires that all variables be on the left-hand side of any equality/inequality signs. This is to say, although [x1] + [X2] + [X3] == 1 is equivalent to [X1] + [X2] == 1 - [X3], having a variable [X3] on the right side of the equality sign (==) will cause the tool to fail with the error: R.exe exit code (3221225512) indicated an error.
If a thorough investigation of your data does not help resolve this error, please search your question on the Designer Discussion forum in the Community, then post your question there to get help from Community users.