SQL Server 2012 PowerPivot Incorrectly Detects ADOMD.NET Causing a Failed Health Rule

When PowerPivot runs the health rule, PowerPivot: ADOMD.NET is not installed on a standalone WFE that is configured for central admin, it checks for a file version of “11.0.0.0”:

The file version is passed from this property in Microsoft.AnalysisServices.AdomdClient.AdomdConnection:

The FileVersion property of the Microsoft.AnalysisServices.AdomdClient.dll (for SQL 2012) is:

11.0.2100.60 ((SQL11_RTM).120210-1917 )

Since that doesn’t compare to “11.0.0.0”, the rule fails.  This rule can be ignored for now, just make sure the proper Microsoft.AnalysisServices.AdomdClient.dll is installed at C:\Windows\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\11.0.0.0__89845dcd8080cc91\.

13 Comments

  1. Thanks for the post, this definitely explains why I am seeing this in a single server farm with a new install (on SQL 2012). Could you tell me where you went to see the code that the SharePoint Health Analyzer is running? I haven’t been able to locate the first set of code you have shown in the post. I looked in the lists in Central Administration and the logs and couldn’t find anything that pointed me in the right direction even. Google and Bing were no better.

    • You need a tool like ILSpy, .NET Reflector, or JustDecompile.

      • That’s pretty awesome. Thank you for such a quick response too! One final question. Was there any particular method you used to figure out which assembly to go searching in when you saw the failed health rule in Central Administration? I would assume (or hope) there is documentation or logging as to what is run for each of those rules someplace.

        Thanks again.

  2. Thanks for this post. I am having a difficult time tracking down the instance of Check() you display – what class is this in?

    • It is in Microsoft.AnalysisServices.AdomdClient.AdomdConnection.

      • Thanks for the quick reply. I must be incredibly dense here – I am not seeing any Check() method in Microsoft.AnalysisServices.AdomdClient.AdomdConnection. (I am opening the assembly which is in the GAC, using JustDecompile.) I do see many overridden Check() methods in classes in the Microsoft.SharePoint.Administration.Health namespace – do those classes have anything to do with this?

        • Alright, I had to go back and look at this, and in SharePoint 2013 I believe there may be changes where this method is located at. At any rate, look in the Microsoft.AnalysisServices.SPAddin.dll and you’ll find a HealthRules class.

  3. Trevor I am using sp2013 Enterprise Farm, where i repeatedly get saem error message you have mentioned above. So when i went to GAC_MSIl i saw 2 versions of AdomdClient ( Version: 9.0.242.0, File Version:9.0.1399.0 ) and (Version:11.0.0.0, File Version:11.0.3000.0). Should i really be having two versions of ADOMD and if i have correct version of the file so that i can ignore the error.

  4. connect from excel 2016 cube analisys service error DataSource.Error: AnalysisServices: Se necesita la versión x86 de ‘ADOMD.NET 11.0’ para ejecutar esta consulta. El proveedor se puede descargar de ‘https://www.microsoft.com/en-us/download/details.aspx?id=35580’.

  5. Pingback: ID: 2138 - PowerPivot: ADOMD.NET ist nicht auf einem eigenständigen, für die Zentraladministration konfigurierten WFE installiert - Die SharePoint-Wiese

  6. Pingback: SQL Server 2016 Power Pivot for SharePoint 2016 Health Rules – ADMOMD.net is not installed – SharePoint and O365

Leave a Reply