SQL Server 2016 Remote Blob Storage (RBS) – Error 1723

Today I tried to install RBS for SharePoint 2016. During the installation progress you have to run RBS.msi on all SharePoint 2016 WFEs. I’m using SQL Server 2016 Enterprise as Database Engine.

RBS.msi 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:

sqlrbs

Let’s hope, Microsoft can fix it. I created a new issue. Any ideas to get round this issue are highly appreciated.

Update 1 (2016-06-15):

After a recent chat with a Microsoft Software Engineer we were able to enclose the error. The error only happens on systems that don’t have SQL 2016 installed.

Update 2 (2016-07-20):

Today I tired the SQL 2014 SP 2 RBS.msi. I was able to test the connection. I’m not sure, if the 2014 RBS.msi is supported with SQL Server 2016 databases.
BTW. the 2014 RBS.msi is about one MB larger than the 2016 RBS.msi

Update 3 (2016-07-21):

SQL 2014 SP2 RBS is not compatible with SQL Server 2016.

The SharePoint Product Group confirmed, that SharePoint 2016 is not yet tested and certified with SQL 2016 RBS. There will be further work to get SQL 2016 RBS certified. SQL 2014 SP 2 RBS is currently the supported version -Currently refer to these two articles:
https://technet.microsoft.com/en-us/library/ff628583(v=office.16).aspx
https://technet.microsoft.com/en-us/library/ee748649(v=office.16).aspx

There will be an further article about SharePoint 2016 and SQL 2016 RBS.

Update 4 (2016-08-09) – Solution

Today Microsoft published a new blog article focusing on the missing DLL issue. The SQL 2016 RBS installer needs the Microsoft ODBC Driver 13 for SQL Server. You can download it here.

Sadly the technet article Overview of RBS in SharePoint Server 2016 isn’t updated yet: “Be aware that SQL Server Remote BLOB Store installation package for SQL Server 2014 is the only version of RBS that is supported by SharePoint Server 2016”.

Office Online Server – MSVCR120.dll missing

Today I installed a new Office Online Server Farm based on two Windows 2012 R2 Servers.

The installation went smooth, but I experienced an unhealthy farm status. Checking the ULS logs I found the following error:

LoadLibrary failed with error 2 on D:\Program Files\Office Web Apps\OneNoteMerge\bin\ONSrvU.DLL

After a bit of investigation, I tried to run the OneNoteMerge.exe. This resulted in the following error:

The program can't start because MSVCR120.dll is missing from your computer.
Try reinstalling the program to fix this problem.

What now?

Checking the c:\windows\system32\ folder I found the following file:

msvcr120_clr0400.dll

Following the Microsoft Deployment Guide for Office Online Server there are the following prerequisites:

  • .NET Framework 4.5.2 (I wasn’t able to install it)
  • Visual C++ Redistributable for Visual Studio 2015
  • Microsoft.IdentityModel.Extention.dll

I install the remaining two prerequisites, but wasn’t able to get rid of the errors.

I found the following article: Determining Which DLLs to Redistribute pointing out, that msvcr120.dll is a part of Visual Studio 2013.

So I went for the Visual C++ Redistributable Packages for Visual Studio 2013 package and downloaded both the x64 and x86 version and installed them. The msvcr120.dll comes with the x64 version.

This solved the error for me. I hope it works in your environment as well.

How to set git upstream

Trying to sync a fork that does not have an upstream repository can result in an error:

fatal: 'upstream' does not appear to be a git repository
fatal: Could not read from remote repository. 

Please make sure you have the correct access rights

To resolve this error check the output of

$ git remote -v

Your output should look like this

UpStreamOwner https://github.com/UpStreamOwner/repository.git (fetch)
UpStreamOwner https://github.com/UpStreamOwner/repository.git (push)
origin https://github.com/yourName/repository.git (fetch)
origin https://github.com/yourName/repository.git (push)

What’s missing is the upstream.

To set the upstream for this fork run the following command:

$ git remote add upstream https://github.com/UpStreamOwner/repository.git

Sharing is caring – a good example

During the last month I was building a new web application with an extensive user interface. There were no requirements focusing on the design. This decision was up to me. What now? I did not want to start from scratch.

I had used the Office UI Fabric in other projects before and was thrilled to get my hands dirty with the ngOfficeUIFabric Angular directives. I started with a simple form which implements few inputs. As the project grew more complex more input fields were needed. By now nearly each directive is in use.

Complex projects are the best test cases for new implementations. With that in mind I wasn’t surprised to find some issues with the ngOfficeUIFabric.

I started to address these issues at the github repo of the ngOfficeUIFabric project and was able to fix some of them myself. By now all of the initial issues I had are fixed.

Mikael Svenson experienced an issue with the uif-textfield directive in multiline mode. In my project the uif-textfield is by far the most popular one. When I saw Mikael’s issue I was glad to help, as I contributed on this directive before. In less than 24 hours the initial issue got resolved. Check out Mikael’s blog about the the awesome community.

After years of consumption, I am very glad to finally being able to contribute to this awesome community as well.

 

ngOfficeUIFabric – the messagebar component

How to use the ngOfficeUiFabric MessageBar directive ?

The message bar is a new Office UI Fabric component, which is part of Office UI Fabric 2.6.1.

DefaultMessageBar
The default message bar component

You can use the message bar to present timely information to provide key information or actions to enrich the user experience.

The message bar supports several levels of information:

  • Default (as shown above)
  • Warning – used in exceptional situations
  • Severe Warning – used situations, that could turn into a harmful one
  • Error – used for serious failure
  • Remove – used when a user faces security restrictions
  • Success – used when something went right.

The messagebar directive

The new umessagebar directive will be a part of ngOfficeUIFabric v0.11.0 release.
Continue reading “ngOfficeUIFabric – the messagebar component”

SharePoint Developer Dashbord

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.

The SharePoint Server 2016 Developer Dashboard
SharePoint Server 2016 Developer Dashboard

How to enable the Developer Dashboard?

Continue reading “SharePoint Developer Dashbord”

SharePoint 2016 and the language packs

Start of SharePoint 2016 Installation
The start of the SharePoint 2016 Installation

Last Wednesday Microsoft released SharePoint 2016. I was able to download it via MSDN during Microsoft’s FutureofSharePoint Event and installed my first SharePoint 2016 Server today.

If you are wondering, where you can find the latest language packs, just follow this link to Microsoft: Language Packs for SharePoint Server 2016

Though they were released in march and SharePoint 2016 got released last week, they do work with SharePoint 2016. I checked with Bill BearAre these language packs up to date?