In a SharePoint 2016 Farm with Power pivot health rules will fail with the following error:
Power Pivot: ADOMD.NET is not installed on a standalone WFE that is configured for central admin
Trevor Seward wrote a great article on this topic focusing on SQL 2012. To verify that his article is still valid for SQL Server 2016 and SharePoint 2016 with Power Pivot, I followed his article:
I installed the latest SQL_AS_ADOMD.msi, which can be downloaded here. But nothing changed.
Here is the content of the Microsoft.AnalysisServices.AdomdClient.dll (13.0.0.0) found under C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\v4.0_13.0.0.0. ….
[SharePointPermission(System.Security.Permissions.SecurityAction.LinkDemand, ObjectModel = true)]
public override SPHealthCheckStatus Check()
{
SPHealthCheckStatus result;
try
{
if (!HealthUtil.isCentralAdminConfiged())
{
result = SPHealthCheckStatus.Passed;
}
else
{
try
{
if (HealthUtil.IsADOMDInstalled("13.0.0.0"))
{
result = SPHealthCheckStatus.Passed;
}
else
{
result = SPHealthCheckStatus.Failed;
}…
A quick check via Power Shell reveals the following
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices.Adomdclient") $connnection = new-object Microsoft.AnalysisServices.AdomdClient.AdomdConnection $connection.ClientVersion
The client version is: “13.0.1601.5 ((SQL16_RTM).160429-2226)” and that is why the rule fails.
Either you disable the rule or ignore it, if Adomd is installed properly.