Index out of Range
CAUSE:This may be caused by the database instance in the source project not matching the database instance in the destination project during migration. When MDX objects are being migrated, the schema is identified with the database instance associated with it. So when the database instances do not match across environments, the objects are not migrated properly.
A reason one may choose to maintain different database instances across environments is to control the data users see. For example, if a user has a Development and Production environment, the Administrator of the system may want developers to see different data than those using the Production environment. By using different database instances across environments, it is possible to have users to see different data. When using MDX cubes as a data source, the database instance associate with a schema can be changed by using Schema Maintenance. For information on how to use schema maintenance, please see
KB35976: Feature in MicroStrategy: Changing a project from using one MDX database instance to another for all objects.
ACTION:To ensure migration completes successfully, the database instance associated to the schema should match in the source and destination project by choosing one of the following set ups:
1) Maintain a single database instance object across environments. These database instances can have different definitions as long as the GUID is the same. This allows for the database instance to point to different databases in each environment. When this method is being used, ensure that the conflict resolution is not set to 'Replace' for the database instance during migration. If the database instance is replaced, then the definition of the database instance in the destination project will change and be replaced by the definition of the database instance from the source project.
2) Maintain 2 database instances, but use Schema Maintenance to change the database instance the schema points to prior to migrating objects. This can be done in either environment. Once migration has completed, Schema Maintenance can be used to change the database instance again.
For more information on migrating MDX objects, see
KB20124: Best practices to migrate cubes (SAP BW, MSAS or Essbase) and cube objects (attributes) using MicroStrategy Object Manager 
