Power View in Excel 2013 and errors

Sometimes you get an error message that doesn't make any sense. "PC Load Letter" is quite a good example (Office Space, a great movie, shows how users react to such messages 😉 ). Here's an interesting one that I got when using Power View in Excel 2013 based on a tabular model:

System.Reflection.TargetInvocationException: System.ComponentModel.Win32Exception (0x80004005): The specified module could not be found

I had created a Power View report on a tabular model with dates, sales amount and the sales amount in the same period as last year. I previously made this in a pivot table based on the tabular model and that didn't give any errors at all. What gives? Why would Power View have errors but not the pivot table? They query the same tabular model after all?

People who have worked with DAX may have used the SAMEPERIODLASTYEAR function and know about the contigious date error. I suspected this may be the problem. But how to find out? I turned on the SQL Profiler and found some interesting things:

To my suprise the pivot table query to my tabular model was an MDX-query and not DAX. So the pivot table had no problem whereas Power View has to use DAX to interact with the Tabular model. Because they use a different query to produce the same report, one gets an error and the other one does not!

In the end, it was the contigious dates error. But the excel error message was not very helpful to figure that out...

 

 

Principal BI consultant at Rubicon

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Next ArticleSSRS - it doesn't have to be ugly..