From a user’s point of view: I really like the Visio Services in SharePoint 2016
From an administrator’s view: finding the source of an error in Visio Services can be a real pain!
Failed to get raster diagram for Visio file: Default Page ID Exception
The error for the user is not very helpful:
Visio Services was unable to display the requested page because it does not exist within this Web Drawing. To resolve this issue, make sure to request a page that exists within this Web Drawing.
The error message in the ULS log – nah:
Failed to get raster diagram for visio file https:///.vsdx page default page ID Exception : System.ServiceModel.FaultException`1[Microsoft.Office.Visio.Server.GraphicsServer.VisioGraphicsServiceFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.Office.Visio.Server.GraphicsServer.VisioGraphicsServiceFault).
I was able to open the document in Visio 2016 and everything looked fine. I compared this file to another, which rendered fine. The difference was very hard to spot: The heading of the tab displayed was italic and not regular as in the good file.
An italic tab name indicates, that this is a background page and not a regular page. After changing the page type, everything worked as expected.
“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.
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.
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
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:
The Developer Dashboard is a part of the SharePoint On-Premise versions. I think this feature is one of the most forgotten and underrated. Especially in large farm deployments it offers a lot of functionality to identify bugs, errors, performance issues and bottlenecks.