Skip Ribbon Commands
Skip to main content

KnowPoint

:

Chris McNulty > KnowPoint > Posts > Why can’t SharePoint Dashboard Designer 2013 connect to SQL Analysis Services 2012?
February 05
Why can’t SharePoint Dashboard Designer 2013 connect to SQL Analysis Services 2012?

I mean, it's simple, right? I'm working on a new build of SharePoint 2013 and the latest version of SQL Server 2012.

I've set up Performance Point many, many times before in SharePoint 2010. But on this build I couldn't connect to my Analysis Services cube. Now, the cube "works", and I can browse it and deploy it from Visual Studio and SQL Enterprise Manager. But not SharePoint!

The database dropdown remained empty. Adding a manual connection string () also Sounded like a security issue, right? Nope – connecting from any combination of administrative, farm, SQL accounts was all blocked. Service account, stored account, or per user – no luck.

 

Next, I tried connecting Dashboard Designer to a classic database engine E Engine SQL database. No issues at all.

Fell back to running a SQL Profiler trace against SSAS, and here I got my first clue – no signs of any failed or successful logins. Sounds like no connection. I confirmed the SQL Server Browser was running and all client default protocols were on. Hmm,

So finally I checked the local event log and saw this (leaving out some details):

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClient, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

Now, I may be a trifle obsessed with SharePoint build numbers, but even I can notice a major SQL version number. Version 10.0.0.0 ? Isn't SQL 2012 internal version 11?

That's the clue. It turns out Dashboard Designer for 2013 was written for the SQL 2008 R2 Analysis Services clients. So you need to download and add client support for ADOMD version 10 from http://www.microsoft.com/en-us/download/details.aspx?id=16978

Just perform an IISReset, and you should be back in business. Hope this helps!

Comments

There are no comments for this post.