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 (18.104.22.168) found under C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\v4.0_22.214.171.124. ….
[SharePointPermission(System.Security.Permissions.SecurityAction.LinkDemand, ObjectModel = true)]
public override SPHealthCheckStatus Check()
result = SPHealthCheckStatus.Passed;
result = SPHealthCheckStatus.Passed;
result = SPHealthCheckStatus.Failed;
A quick check via Power Shell reveals the following
$connnection = new-object Microsoft.AnalysisServices.AdomdClient.AdomdConnection
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.
In the last few weeks I tried to enable SQL Server 2016 Remote BLOB Storage (RBS) for SharePoint Server 2016. As mentioned in my earlier post I had no success installing the SQL Server 2016 RBS components on my SharePoint 2016 WFEs.
By now I was able to install and configure SQL Server 2016 RBS for SharePoint 2016 and I want to share my experience.
In the moment Microsoft is certifying SQL Server 2016 RBS for SharePoint Server 2016. By now be prepared to experience some minor issues. For SQL Server 2014 RBS there is additional information available here.
Continue reading “SharePoint 2016 with SQL Server 2016 RBS – Installation Guide”
Microsoft changed main parts of the BI capabilities with SharePoint 2016. SharePoint Server 2016 does no longer provide Excel Services. Excel Services are now part of the Office Online Server, which got released on May 4, 2016. With the November 2016 Release Microsoft supports even embedded Power Views in Excel Online.
So what’s new about it?
As Excel Services being no longer part of SharePoint 2016 and now part of the Office Online Server, there have to be other changes too. Not so well publicly announced, there are some hidden requirement for BI scenarios:
SharePoint 2016 requires SQL Server 2016 for BI scenarios
Ricardo Muti wrote a great article about “Integrate Reporting Services into SharePoint 2016” in which he addresses the upcoming changes to the reporting infrastructure of SP 2016.
If you want to get started right now, grab your copy of the white paper: Deploying SQL Server 2016 PowerPivot and Power View in SharePoint 2016.
If you plan the deployment in a multi server farm: Deploying SQL Server 2016 PowerPivot and Power View in a Multi-Tier SharePoint 2016 Farm
Continue reading “SharePoint 2016 – Business Intelligence”
Today I tried to install and configure my SharePoint Server 2016 Farm to use the SQL Server 2016 remote BLOB storage (RBS).
I started with the following environment. All servers are virtualized on hyper-v and are running Windows 2012 R2 as operating system.
- 1 Domain Controller
- 1 SQL Server 2016 Enterprise
- 1 SharePoint Server 2016 Custom Role
- 1 SharePoint Server 2016 Web Front-End role
The RBS setup for SharePoint Server consists of several parts. See my installation guide here. Which goes into the details for configuring the SQL Server 2016 and reflects the latest Update 4 (see below).
The RBS installation requires to run the RBS installer (part of the Microsoft SQL Server 2016 Feature Pack: RBS.msi) on each SharePoint Web Front-End Server.
The RBS installer can be found on the SQL 2016 ISO under: ..\x64\redist\RemoteBlobStore\RBS.msi or it can be downloaded from: Microsoft SQL Server 2016 Feature Pack
Sadly I ran into the following issue during the installation on my SharePoint 2016 Web Front-End:
Continue reading “SQL Server 2016 Remote Blob Storage (RBS) – Error 1723”