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”
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”
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.
Checking the c:\windows\system32\ folder I found the following file:
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
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.
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
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.