Office Web Apps for SharePoint on-premise

My Office Web Apps (Office Online Server--OOS--in my case) server stopped rendering Office Docs with an error:


Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word.


The error also included a session ID. I was able to find the session ID in the ULS logs but it didn't seem to help as the error was quite generic. I had a load balanced pair. It made troubleshooting less than ideal.


Nothing I did to try and resolve it made any difference. Configuring OOS or reconfiguring is really super simple and requires only a few minutes of downtime. It's so quick to rebuild OOS or OWA by following these steps in this link:
https://blogs.technet.microsoft.com/office_web_apps_server_2013_support_blog/2013/12/20/office-web-apps-2013-rebuild-your-farm-in-a-few-easy-steps/


Open PowerShell and let's fix it!


Remove-OfficeWebAppsMachine on both OOS servers. Reboot after the command completes.


Next I ran this command on the "first" OOS server (Quotes around the certificate name and URL are getting stripped out of this page):

New-OfficeWebAppsFarm -InternalURL "https://OOSserver.fqdn.domain.com"  -EditingEnabled -OpenFromURLEnabled -CertificateName "cert-friendly-name"


On the second, load balanced OOS machine I ran this command:
New-OfficeWebAppsMachine -MachineToJoin OOSserver.fqdn.domain.com


Then on one of the SharePoint servers I ran these two commands:

Remove-SPWOPIBinding -All:$true
New-SPWOPIBinding -ServerName "OOSserver.fqdn.domain.com"


Tested and it worked! Quick rebuild and back online in a few minutes!

Comments

Post a Comment

Popular posts from this blog

Exchange 2010 event errors 2601, 2604, 2501

In a recent migration from Exchange 2003/2007 to Exchange 2010, I ran into an issue where I had 2601, 2604, and 2501 errors. Log Name:      Application Source:        MSExchange ADAccess Date:          4/8/2013 12:02:20 PM Event ID:      2601 Task Category: General Level:         Warning Keywords:      Classic User:          N/A Computer:      Exchange10.domain.org Description: Process MSEXCHANGEADTOPOLOGY (PID=1268). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account - Error code=8007077f.   The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. and Log Name:      Application Source:        MSExchange ADAccess Date: ...
Read more

"The following factors also affect the level of access for" user with excess permissions

Image
I have a user that had access to site settings, all content, etc. I double checked her access and it was read only but the permissions check tool showed a panel beneath the site permissions that showed Allow for many categories. She had full control. "The following factors also affect the level of access for" She was added as a Site Collection Administrator. I don't know who would have added her there, but someone had. If you find this type of issue, that should be the first thing you check. You can also check the Web Application User Policy in Central Admin. That's the other area I find people or groups with elevated permissions.
Read more

Robocopy Error 31 A device attached to the system is not functioning

I was migrating Windows file shares to NetApp CIFS shares using Robocopy. I was unable to copy owner information or NTFS Security (/COPY:DATSOU) without getting this Error: ERROR 31 (0x0000001F) Copying NTFS Security to Destination Directory F:\PATH A device attached to the system is not functioning. I thought it may be the zone information on may of these files. I used the Sysintenals Streams utility to remove that information. It did not help. In the end, I was forced to copy without NTFS information (/COPY:DATU) When I viewed the properties of any share, folder, or file, the length of time to enumerate and display the permissions was exceedingly slow. I tried disabling anti-virus, etc. In the end, I had to manually re-create the permissions after the initial data copy. File ownership information was lost. UPDATE: I ran a CHKDSK /F and following a reboot this robocopy functioned fine.
Read more