Mar 01 2018 04:02 AM - edited Mar 01 2018 04:05 AM
Hi
This is a tale of 2: Office Online Servers . Both
PS C:\New-SPWOPIBinding -ServerName OOS.mydomain.com WARNING: The server did not respond. Trying again (attempt 1 of 5). WARNING: The server did not respond. Trying again (attempt 2 of 5). WARNING: The server did not respond. Trying again (attempt 3 of 5). WARNING: The server did not respond. Trying again (attempt 4 of 5). WARNING: The server did not respond. Trying again (attempt 5 of 5). New-SPWOPIBinding : Sorry, we have encountered an error and New-SPWOPIBinding has failed. If you are using a server configured with HTTP, you must include the -AllowHTTP parameter. At line:1 char:1 + New-SPWOPIBinding -ServerName OOS.mydomain.com + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Microsoft.Share...tNewWOPIBinding:SPCmdletNewWOPIBinding) [New-S PWOPIBinding], SPCmdletException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewWOPIBinding
Recreated the OOS Farm without any issues>
I can validate https://OOS.mydomain.com/hosting/discovery ok
I have checked Port 443 access from the WFE to OOS, also OK
The log location seems a work of fiction! Any ideas anyone please.
Mar 02 2018 05:49 AM
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
Mar 02 2018 08:15 AM
SolutionMar 02 2018 08:32 AM
I think you are on to something there.
You can always enable CAPI2 logging for a detailed error (and what Trevor said) :) .
-Mike
Mar 03 2018 10:34 AM
Mar 05 2018 05:01 AM
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.
Mar 05 2018 05:07 AM - edited Mar 05 2018 05:09 AM
Mike, what is CAP12 logging btw ?
I did manage to locate the (hidden) ULS log dir in the end after a number of system prompts .....
C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
Jul 17 2022 12:44 AM
Worked like a charm all the time "time was the issue" @Daniel Westerdale
Mar 02 2018 08:15 AM
Solution