Forum Discussion

Iron Contributor

Mar 01, 2018

Solved

New-SPWOPIBinding : Sorry, we have encountered an error and New-SPWOPIBinding has failed.

Hi This is a tale of 2: Office Online Servers . Both Both Patched with November 2017 PU Both single instance OOS farms created with a self-cert using the same PS script Both working...

2016

sharepoint server

Trevor Seward
Mar 02, 2018
Have you added the cert to both the trusted root store in the certificates mmc as well as a trusted root in SharePoint central admin?

Daniel Westerdale

Iron Contributor

Mar 02, 2018

All

I suspect this might be my issue. Is there a time problem as it is out of sync between the two servers? Trevor Seward

Trevor Seward

MVP

Mar 02, 2018

Have you added the cert to both the trusted root store in the certificates mmc as well as a trusted root in SharePoint central admin?

Daniel Westerdale
Iron Contributor
Mar 05, 2018
Hi

This morning. I imported an internal cert created by one of my colleagues and recreated the SPWopi farm then attempted to the SPWOPIBinding command:

New-SPWOPIBinding -ServerName OOS1.mydomain.com

- No success ;-(

Next I imported the cert in the trusted root store as you suggested and immediately, I was able to create a SPWOPI binding. I repeat the same steps for the other OOS instance.

Once thing we noticed is the additional step of importing the same cert on OOS into the Trusted Root Certificate Authorities on OOS instance.

Thanks for you excellent advice.