EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB30187: "Index was outside the bounds of the array" error occurs when using MicroStrategy Cube Advisor with a MicroStrategy Enterprise Manager data file


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article notes file restrictions for the Cube Advisor for Enterprise Manager data

SYMPTOM
While running Strategy Cube Advisor, the following error may be encountered after reports have been analyzed for Intelligent Cube structures that would satisfy those reports’ using the Dynamic Sourcing feature introduced into Strategy OLAP Services.

ka02R000000kVdRQAU_0EM440000002EXH.gif

 
Index was outside the bounds of the array
Strategy Cube Advisor can use auxiliary information from a Strategy Enterprise Manager report, “Report Request Statistics per Project,” to prioritize reports that are executed more often and maximize the impact of Dynamic Sourcing. This error may occur if an Enterprise Manager file is provided, while the Cube Advisor runs successfully without the Enterprise Manager file.

ka02R000000kVdRQAU_0EM440000002EXA.gif

 
CAUSE
This error can occur because the Enterprise Manager file is in the wrong format. The file should be provided in plain text format, tab-delimited. It is not supported to use an .xls file here.
The general workflow of Strategy Cube Advisor is as follows: 

  1. Generate metric levels logging data from the Intelligence Server. This is done automatically when analyzing reports from the Cube Advisor graphic user interface (GUI), or it may be done manually outside of the Cube Advisor interface by normal report execution or Strategy Integrity Manager.
  2. Analyze the metric levels log in conjunction with the optional Enterprise Manager data. This creates a cube details file named .details.txt.
  3. Read the cube details file and allow the user to review the proposed Intelligent Cube structures.
    If desired, automatically create Intelligent Cube reports in the project metadata.

If the file is a Microsoft Excel worksheet, Strategy Cube Advisor creates an invalid cube details file. Reading the corrupt file causes the above indexing error.
 
ACTION
Ensure that the Enterprise Manager data file is in the proper format.
The Strategy OLAP Services Guide PDF manual includes instructions to generate the Enterprise Manager data file, either from Strategy Developer Strategy Web. Exporting the Enterprise Manager report from Strategy Web, according to those instructions, will produce the file in the correct format. If the report is exported from Strategy Developer, it is necessary to open the Excel workbook in Microsoft Excel and resave it as Text (Tab delimited).

ka02R000000kVdRQAU_0EM440000002EXI.gif

 
For more details on the use of Strategy Cube Advisor, consult the Strategy OLAP Services Guide PDF manual.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017