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.
Today I faced a problem with OneNote 2016 and OneNote notebooks stored in SharePoint 2016 on premises.
Opening the Notebook the first time – everything was fine. The mouse worked as expected. As soon as I wanted to synchronize my notebook, a authentication prompt was shown. After entering my credentials OneNote started to sync.
BUT: I was no longer able to move the cursor with the mouse.
How to solve this issue?
First: a quick search on google.
There are plenty of results and discussions on this topic.
Here are the steps to solve this issue:
- Internet Explorer – Security Settings
- Options > Security > Trusted Sites
- Add your SharePoint and MySite URLs
- Windows Credential Store – Store your Credentials
- New windows credentials
- Enter the URL of your SharePoint server
- Enter your login-Information
- Repeat 1 for all other SharePoint web applications
“SharePoint Health Analyzer is a feature in Microsoft SharePoint Foundation 2010 that enables administrators to schedule regular, automatic checks for potential configuration, performance, and usage problems in the server farm. Any errors that SharePoint Health Analyzer finds are identified in status reports that are made available to farm administrators in Central Administration.” (MSDN)
In some scenarios SharePoint Health Analyzer helped me out a lot. The messages give a clear starting point to search for the error source. But, there is one thing that bothers me a lot. SharePoint Health Analyzer relies on Time jobs which are usually run on a hourly to weekly schedule. Therefore if you are trying to fix a reported issue there won’t be no immediate feedback.
Continue reading “Start all SharePoint Health Analyzer Jobs”
Today I was not able to test my new developed Office Add-In for Microsoft Excel 2016 on my system and simultaneously on an IIS server.
I noticed the following behavior:
- Runing my Office Add-In from Visual Studio – everything went smooth
- Runing the same Add-In loaded from my App Store – didn’t work
Office tried to load the Visual Studio ‘version’ from of my Office Add-In instead the App Store and server-based one.
Continue reading “How to find the manifest of an installed Office Add-In”
Updating Office Online Server is not as easy as you would expect. It does require some efforts in planning and doing. This technet article is very well written: Apply software updates to Office Online Server. I want to share my experience on updating Office Online Server as there are many pitfalls on the way!
Warning! Do not:
use Windows Update
“Applying Office Online Server updates by using the automatic updates process isn’t supported with Office Online Server. This is because updates to an Office Online Server must be applied in a specific way, as described in this article.” (Source: Apply software updates to Office Online Server)
Continue reading “How to update Office Online Server”
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”