Office Online server not working with SP 2019

Question

Hello Experts,

I have SharePoint 2019 on premise along with "Office online Server installed in windows server 2016 ".
After OOS binding I can see all the office template when clicking on new button in the document library, but when I am trying to open the office document it's showing blank page in the browser. Could you please suggest me, what could be wrong here?

Kind Regards,
Satyendra Paul

Answer 1

Hi Paul,

ensure, that your OOS server can resolve the IP adress of one sharepoint server. You can do it with ping <url> e.g. ping https://mysharepoint.com

The way OOS works is folllowing:

User makes a request from SharePoint -> SharePoint redirects to OOS -> OOS wants to redirect back with rendered document.

best regards
Serkar

Answer 2

Hi Paul,
Hope this will help:
https://learn.microsoft.com/en-us/office/troubleshoot/powerpoint/office-opens-blank-from-sharepoint

Thanks for your time.
Best regards,
Danny

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

FYI: The latest documentation on Office Online Server can be found at:

https://learn.microsoft.com/en-us/officeonlineserver/configure-office-online-server-for-sharepoint-server-2016/configure-office-online-server-for-sharepoint-server-2016

Regarding Excel, the documentation does mention enabling SOAP API on the SharePoint Server:

Step 4: Enable the Excel SOAP API
The Excel SOAP API is needed for scheduled data refresh with Excel Online, and for Excel Web Part rendering. To enable the Excel SOAP API, you need to add the WopiLegacySoapSupport property to the SharePoint Server farm properties using by PowerShell. The input parameter is the URL to ExcelServiceInternal.asmx. This URL can address multiple OOS servers via load balancing. Simply replace the <string> with your Office Online Server path.

To enable the Excel SOAP API, run the following PowerShell where <URL> is the URL of your Office Online Server farm. (For example, https://OfficeOnlineServer.contoso.com.)

$Farm = Get-SPFarm  
$Farm.Properties.Add("WopiLegacySoapSupport", "<URL>/x/_vti_bin/ExcelServiceInternal.asmx");  
$Farm.Update();  

Also, I wanted to share solutions to a couple issues I had with Office Online Server/OfficeWebApps.

1) TLS Support Issues:

As we're upgrading from SP2013 to SP SE and Office Web Apps to Office Online Server, I wanted to test out a newly installed Office Online with SP2013. It wasn't working for some reason with a vague error message that something went wrong in the window where the office document was supposed to show.

Eventually, I ran Get-OfficeWebAppsFarm on the Office Web Apps server and found that the farm information reveals the location of the ULS logs for Office Online. As I had suspected, the issue turned out to be that the newly installed Office Online Server wasn't configured to support TLS1.2 and my old SP2013 server was configured to not support older TLS versions. (There were entries in the ULS log indicating there were TLS session errors.)

You should ensure you have the latest patch installed and enable TLS1.2 support.

https://learn.microsoft.com/en-us/officeonlineserver/enable-tls-1-1-and-tls-1-2-support-in-office-online-server

Hope this helps!

2) Office Online Server and SharePoint in Network Load Balanced Scenario

I was having an issue where Office Online wouldn't work when My SharePoint Server and Office Online servers were set up in a Load Balanced configuration with port rules for 80 and 443.

I was able to resolve this by removing the port rules and specifying the default port rule for all ports (0-65535), Both TCP and UDP, Single Affinity. I had to do this for both the SharePoint NLB and OfficeOnline NLB settings.

One theoretical scenario is that the communication traffic between the two servers would be getting routed back to the wrong server when communicating on ports not managed by NLB. Therefore, configuring NLB to manage the traffic for all ports with single affinity resolves this issue.