The R Integration Pack is no longer supported as of December 2024.

Troubleshooting R Integration in MicroStrategy

The following table lists error messages that are potentially caused when performing R statistical analysis in MicroStrategy by creating a metric that includes statistical analysis from an R script (see Chapter 3, Performing statistical analysis). A MicroStrategy user who creates metrics, reports, documents, and dashboards that include R statistical analysis can review the resolutions listed below to troubleshoot any problems.

Error message	Cause	Resolution
Valid script repository must be specified if using relative R script filename.	The _RScriptFile parameter of the metric expression includes only an R script name and the R script repository for the computer could not be found.	Ensure that the R script is stored in the R script repository for the computer.
Missing R script file name.	The _RScriptFile parameter is empty.	Define the _RScriptFile parameter in the metric expression. You can retrieve the original metric expression from the R script, as described in Retrieving the metric expression. If the _RScriptFile parameter is also empty in the R script, contact the developer of the R script to determine its location.
R script file 'Script' not found. Where 'Script' is the name of the R script.	The R script could not be found in the specified location.	Ensure that the R script is stored in the location specified in the _RScriptFile parameter.
Error opening R script file 'Script'. Where 'Script' is the name of the R script.	The permissions for accessing the R script prevent opening the R script.	Ensure that you have the required permissions to access the folder where the R script is stored and the R script itself.
The output Output specified in the _OutputVar parameter is not defined. Where Output is the name of the output variable.	The _OutputVar parameter has been modified when creating a metric.	Ensure that the _OutputVar parameter for the metric is defined with a valid value.
The actual number of inputs (InputCount) does not equal to the number of inputs specified within the R script (InputRVARCount). Where: InputCount is the number of inputs used when executing the R script. InputRVARCount is the number of inputs defined in the header block of the R script.	The _CheckInputCount parameter is defined as True and the number of metrics included in the metric expression is not valid for the inputs required for the R script.	Ensure that you have provided metrics for each input included in the metric expression. You can retrieve the original metric expression from the R script, as described in Retrieving the metric expression. If the correct number of metrics appears to be included but you continue to receive this error, contact the developer of the R script to determine the expected number of metrics that should be included in your metric expression.
The actual number of inputs (InputCount) is less than the number of inputs specified within the R script (InputRVARCount). Where: InputCount is the number of inputs used when executing the R script. InputRVARCount is the number of inputs defined in the header block of the R script.	The _CheckInputCount parameter is defined as True and the number of metrics included in the metric expression is less than the inputs required for the R script.	Ensure that you have provided metrics for each input included in the metric expression. You can retrieve the original metric expression from the R script, as described in Retrieving the metric expression.
The actual number of inputs (InputCount) is not consistent with the number of inputs specified within the R script (InputRVARCount). Where: InputCount is the number of inputs used when executing the R script. InputRVARCount is the number of inputs defined in the header block of the R script.	The _CheckInputCount parameter is defined as True, at least one input variable can accept multiple inputs, and the number of metrics included in the metric expression does not match with the allowable number of inputs that can be passed back to R.	Ensure that you have provided metrics for each input included in the metric expression. Inputs for R can support multiple metrics as their input. Contact the developer of the R script to determine the expected number of metrics that should be included in your metric expression.
Actual data type DataType for input variable 'Input' is not supported. Where: DataType is the data type for the metric mapped to an input variable. Input is the name of the input variable. RDataType is the data type retrieved from R.	The data type for the metric mapped to an input variable is not compatible with the input variables data type defined in R.	Ensure that you have provided the correct metric for the input variable specified in the error message and that the metric's data type is correct. If no changes to the metric are needed, contact the developer of the R script to determine if the input variable is using the correct data type.
Actual data type DataType for input variable 'Input' is not compatible with the expected data type RDataType. Where: DataType is the data type for the metric mapped to an input variable. Input is the name of the input variable. RDataType is the data type retrieved from R.	The data type for the metric uses a data type that is not supported for passing information back to R.	Modify the data type for the metric that is mapped to the input variable specified. Supported metric data types include: Short Integer Float Double String UTF8 string
The input variable 'Input' contained nulls which were skipped due to nullprocessing settings. Failing report to avoid potential pairing-up problems.	The _NullsAllowed parameter for the metric is defined as False, and multiple metrics were mapped to input variables that contained null values.	You can ignore this warning message and allow null values to be passed back to R by defining the _ NullsAllowed parameter for the metric as True.
Invalid _InputNames value: Nested brackets not allowed.	Nested brackets (bracket characters are []) are included in the _InputNames parameter value, which is not a valid syntax. This can occur if you updated the metric's _ InputNames parameter.	A single set of brackets is required if an input name includes a space or other special character. Update the metric expression for a metric to ensure that all nested brackets are removed. For example: Incorrect syntax: [_ InputNames]="Input1, [[Input 2]], Input3" Correct syntax: [_ InputNames]="Input1, [Input 2], Input3"
Invalid _InputNames value: Missing comma separator before opening bracket.	A comma is missing between the input variables included in the _InputNames parameter value. This can occur if you updated the metric's _InputNames parameter	Update the metric expression for a metric to ensure that a single comma is used to separate each input variable. For example: Incorrect syntax: [_InputNames]="Input1 [Input 2], Input3" Correct syntax: [_InputNames]="Input1,[Input 2], Input3"
Invalid _InputNames value: Missing opening bracket.	A closing bracket (]) does not have a matching opening bracket ([) within the _InputNames parameter value. This can occur if you updated the metric's _InputNames parameter.	Update the metric expression for a metric to ensure that matching opening and closing brackets are included. For example: Incorrect syntax: [_ InputNames]="Input1, Input 2], Input3" Correct syntax: [_ InputNames]="Input1, [Input 2], Input3"
Invalid _InputNames value: Zero-length names not allowed.	An input variable is missing from the _InputNames parameter value or an extra comma was included. This can occur if you updated the metric's _InputNames parameter.	Update the metric expression for a metric to ensure that each input variable is included and multiple commas are not included sequentially. For example: Incorrect syntax: [_ InputNames]="Input1,, Input3" Correct syntax: [_ InputNames]="Input1, Input2, Input3"
Invalid _InputNames value: Missing closing bracket.	An opening bracket ([) does not have a matching closing bracket (]) within the _InputNames parameter value. This can occur if you updated the metric's _InputNames parameter.	Update the metric expression for a metric to ensure that matching opening and closing brackets are included. For example: Incorrect syntax: [_ InputNames]="Input1, [Input 2, Input3" Correct syntax: [_ InputNames]="Input1, [Input 2], Input3"
Invalid _InputNames value: Number of names does not match the actual count.	The number of input variables included in the _InputNames parameter value is different than the R script. This can occur if you updated the metric's _InputNames parameter.	Ensure that the number of input variables specified is consistent with the specified R script. You can review the metric expression in the R script to confirm the number of input variables before any changes were done for the metric (see Retrieving the metric expression).