Office Online Server Showing “Unhealthy” Status

*UPDATE* The new version of Office Online Server released on 11/17/2016 has health fixes in place. You may still get a OneNoteMerge health error in the event log like this: <?xml version=”1.0″ encoding=”utf-16″?> <HealthReport xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”> <HealthMessage>WebOneNoteWatchdog reported status for OneNoteMerge in category ‘Ping’. Reported status: OneNote Merge Ping test failed. OneNoteMerge.exe not available to execute…

13

Office Web Apps Server 2013 with .NET 4.6+

Problem: When using .NET 4.6+ the Office viewers or op/generate.aspx will not work and give the following “This page can’t be displayed” error. Cause: The new .NET Framework version 4.6 and higher includes a new Just-In-Time (JIT) compiler. Solution: A couple of workarounds are detailed here (https://github.com/Microsoft/dotnet/blob/master/docs/testing-with-ryujit.md#net-framework-46—troubleshooting-ryujit) The easiest workaround identified is to use the following registry…

0

Office Web Apps 2013 External Users

Hello Everyone, The point of this blog is to help you understand your options when configuring OWA to work with external users. There is one major configuration issue with this, that is that office web app calls need to be passed through, seemingly, without being challenged. In lync 2013 there are articles that talk about the configuration…

0

Configure ARR as a reverse proxy for Office Web Apps 2013 external users

With the Application Request Routing service becoming more widely used it was felt that it would be good to touch on how this can be used as a reverse proxy for Office Web App deployments. (this does not cover how to install the ARR software on the server or configuration for external sharepoint use). 1….

0

Deploying the Office Web Apps Server 2013 – "Microsoft Office Web Apps Server 2013 Encountered an error during setup"

If you are planning to deploy an Office Web Apps Farm, the following data could be useful for you in case you are encountering the "Microsoft Office Web Apps Server 2013 Encountered an error during setup" error while running the installation package.It specifically happens on virtual environments with Windows Server 2012 (R 2) and the error looks like…


Clarifications on Dropbox integration with Office Online

Over the past month, we've spoken to many customers regarding our newly released Dropbox integration for Office Online. The Office announcement blog HERE does a great job of illustrating what the integration does and how it works. However, our customers brought up some very valid concerns regarding the integration. So we wanted to quell some of…


"To start seeing preview, please log on by opening the document"

ISSUE: Document preview for SharePoint 2013 search results randomly give an error "To start seeing previews, please log on by opening the document". CAUSE: The behavior occurs because the page that we use to show the preview (_layouts/15/wopiframe.aspx) is set up for anonymous access.  Since the user did not browse the site collections from where the documents to…

0

SharePoint Search and Excel Interactive Preview: "404 – File or directory not found."

For the past several months I have worked on an issue with the Excel Interactive Preview throwing the error: "Server Error404 – File or directory not found.The resource you are looking for might have been removed,had its name changed, or is temporarily unavailable." When refining a SharePoint Search: We have determined the root cause and this…

3

Office Web App 2010 Viewers do not work, System.ServiceModel.EndpointNotFoundException, when Nintex is running

Overview: You have Office Web Apps 2010 installed, Word and PowerPoint viewing does not work, but the editing does. The appserverhost.exe process is crashing on startup, with error: System.ServiceModel.EndpointNotFoundException  "There was no endpoint listening at net.pipe://127.0.0.1/e31bfd4c-5d98-4dc3-8232-5d2601ca814d that could accept the message. This is often caused by an incorrect address or SOAP action…."   Cause: The SharePoint…

0