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

KB42907: "Index out of range" error message appears when opening the MDX Cube Catalog in MicroStrategy Developer 9.x - 10.x using SAP BW


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical note describes an error that occurs when trying to open the MDX Cube Catalog to connect to an SAP BW data source.

SYMPTOM:
When entering the MDX Cube Catalog the user receives the error "Index out of range" and they cannot open the MDX Cube Catalog to import MDX cubes or to view the structure of existing cubes.  In this case, reports can still be successfully executed against the MDX data source.
 

ka02R000000kVGwQAM_0EM440000002Cst.png

 
CAUSE:
This is a known issue with Strategy Developer 9.3.x - 10.x.  There are 2 specific criteria that cause the issue to occur.  1) The project source is setup to use Windows Authentication and 2) the SAP database instance has "additional connection string parameters" to allow Strategy to use SNC authentication (Secure Network Communications) to connect to the warehouse.
 
Project Source Authentication mode:
 

ka02R000000kVGwQAM_0EM440000002Csg.png

 
Database Instance Connection Settings:
 

ka02R000000kVGwQAM_0EM440000002Csr.png

 
ACTION:
Strategy is investigating the issue and will continue posting updates as soon as they become available.
 
WORKAROUND:
The defect is specific to when the project source is using Windows Authentication and the database instance is using the additional SNC parameters in conjunction.  Changing one of the two will allow the user to open the MDX Cube Catalog without error. 
 
1) Modify the Project Source to use Standard Authentication (or any other form of authentication offered within the Project Source)
 
or
 
2) Modify the database instance so that the "additional connection string parameters" are not needed.  This will leave the database instance unable to connect to the SAP cubes using Secure Network Communications.
 
 
KB414781


Comment

0 comments

Details

Knowledge Article

Published:

June 7, 2017

Last Updated:

June 8, 2018