Category Archives: Errors

Index out of range in method ‘IDSSTemplateMetrics::Remove’…

Hello there!

Today let’s talk about an error that occurs sometimes while working with documents in MicroStrategy. 

This error: Index out of range in method ‘IDSSTemplateMetrics::Remove’… appears when you are trying to run a document and it doesn’t allows you to execute it. 

The problem happens when a component in your document gets an error. 

You will need to look for this component, remove it and recreate it. 

I always begin removing selectors. Remove all, run… If it is works, your problem is in a selector that you removed. Try to find which one or ones are occurring this error.  Remove it, and recreate it. 

If your error continues, start removing panel stacks, after that grid and then graphs. 

Remember to remove and recreate the components with problems. 

Hope it helps you. 

God bless you!

Solving: Path ./WEB-INF/jsBundleDescs/mojo-acl.txt does not start wigh a ‘/’ character (

Hello there!

Today let’s talk about an error that can be caught in MicroStrategy Web. The msg is:

Path ./WEB-INF/jsBundleDescs/mojo-acl.txt does not start wigh a '/' character

To solve this problem, just create a file with the name of mojo-acl.txt and put inside your WEB-INF/jsBundleDescs folder.

Inside the file, just write:


Clear web cache and restart your Web Server.


God bless you!

The column %1’s datatype %2 with precision %3 scale %4 is not supported

Hello there!

Today let’s talk about a common error in MicroStrategy while mapping a new Attribute:

The column %1’s datatype %2 with precision %3 scale %4 is not supported…


Sometimes MicroStrategy can’t get the exact data type from Database while creating a new form attribute.

It’s always a good idea to take a look at “Column Alias” while editing or creating a new attribute, because an unknown data type could appears there, just like the image below:


That is the reason that makes this error happens. So, lets solve this problem!

1. Edit your attribute -> Click on Modify -> click on Column Alias tab -> click “Modify” -> Click on “New” button” -> Give a name and the correct data type.






After that, update your schema and you will be fine again!

Hope it helps!

God bless you!