MicroStrategy 9.5.0 Compatibility Issue with SQL Server 2014

Hi All,

Recently I have been evaluating MicroStrategy 9.5.0 and its been a rebranding of MicroStrategy 9.4.1 with advanced security features and little functionalities.

Though Microsoft SQL Server 2014 is supported from MicroStrategy 9.4.1 onwards its does have a small compatibility issue with Microsoft SQL Server 2014.

I was running with MicroStrategy v9.5.0 and I get this error "Failed to create component ‘Server Administrator’; CoCreate Instance Returned 0x8007007E" after upgrading my database server from SQL Server 2012 to SQL Server 2014.

And it so happened after the upgrade to SQL Server 2014 MicroStrategy developer doesn't work when trying to log into the project source! and ends up in the below error.

Though MicroStrategy had already documented this issue in the TN below, the workaround suggested did not work out.

http://community.microstrategy.com/t5/Architect/TN47489-quot-Failed-to-create-component-Server-Administrator/ta-p/197123

Troubleshooting steps:

Tried repairing the MicroStrategy Installation - Did not work out

Tried downloading the MicroStrategy setup file, reinstalled Microsoft Windows 7 and installed MicroStrategy 9.5.0 again - did not work out.

So far what I have seen both the above instances which din't work out when I had SQL Server 2014 installed on my PC. Then I installed SQL Server 2012 in my machine and then installed MicroStrategy v9.5.0 then Developer worked like a charm!

Bottomline

 I think there is some compatibility issue with SQL Server 2014 and MicroStrategy v9.5.0. 

My First MicroStrategy Product Limitation! - Projects with Partition Mapping not generating Optimized Report SQL

Hi All,

Is been a while since I have updated the blog! But this time its about my first MicroStrategy Product Limitation!

For some reason MicroStrategy Projects until v9.5.0 implemented with Partition Mapping do not generate optimized report SQL’s on certain reporting scenarios.
In one of our project environments we have projects implemented with and without Partition Mapping feature. We use Partition Mapping feature basically to overcome split DWH architecture.

Please refer the link for info. The issue was reproducible in v9.4.1 and v9.5.0 project environments. The attached document is reproduced from Customer Analysis Module.

It would be great if we could get a resolution for this! Happy Exploration.