Hi

I am stumped.  I have a working Skype for business implementation with two enterprise front end nodes.  I setup a Office Web Apps server, ran the set-officewebappsfarm command as noted in several blogs and configured in internal URL with an internal certificate. I then setup the Office Web Apps server in the topology and associated it with the enterprise pool, published the topology and waited for the event log entry saying it was successful. 

This implementation is completely internal and as far as I know should have no need to access the internet at this point.

Unfortunately I keep getting the following error on the S4B Front End Node:

Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.

Attempted Office Web Apps Server discovery Url: https://ows-001.XXXXXXX/hosting/discovery

Received error message: The remote server returned an error: (407) Proxy Authentication Required.

The number of retries: 2, since 24/07/2015 08:38:06.

Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.

Resolution:

Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.

The Office Web App Server gets the following error both in the event log and bespoke logs

<?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>ProofingWatchdog reported status for Proofing in category 'PositiveWeb'. Reported status: Spelling attempt exception for "good": System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.

   at System.Net.HttpWebRequest.GetRequestStream(TransportContext&amp; context)

   at System.Net.HttpWebRequest.GetRequestStream()

   at Microsoft.Office.Web.Watchdogs.ProofingWatchdog.WebCheck(Uri uri, String word, HealthResult&amp; errorResult, HealthCategory healthCategory)

   at Microsoft.Office.Web.Watchdogs.ProofingWatchdog.WebCheckPositive(Uri uri)</HealthMessage>

</HealthReport>

I have performed the following troubleshooting:

-I can browse to the discovery URL and received the XML response

-I have removed the server from the topology, republished and added it back in again.

-I have confirmed that the local system has no proxy set (through psexec -I -s cmd and netsh winhttp show proxy)

-I have checked get-OfficeWebAppsFarm and confirmed there is no proxy set, clipart and translation is disabled.

-Rebooted all servers many times

-The proxy log shows the following attempts from the server IP:

https://settings-win.data.microsoft.com:443

https://vortex-win.data.microsoft.com:443

Any help would be appreciated

Cheers

Steven

• Edited by steve-2001 Friday, July 24, 2015 10:12 AM

Hi 

Check if the  certificate being used by the wac server on https://wac server/hosting/discovery is correct one 

If you find a wrong one then you can do the below 

Remove the office web apps farm, reboot the server and recreate the web apps farm. Verify if the correct certificate is used

re-run the Lync Server Deployment Wizard to update the Lync component on Front End Server

Also it may be due to .net framework 4.5 not register with IIS, to resolve that you can run following command from Microsoft.net framework folder.

To be specific, the path should be %SYSTEMROOT%\Microsoft.NET\Framework\v4.5\aspnet_regiis.exe -i

Hi

The certificate is an internal one just for the FQDN, not the NetBIOS, but the topology only references the FQDN?  When browsing from an external machine I can reach the /hosting/discovery page with a valid certificate chain.

Should I try the .net 4.5 fix even thought the XML is working?

Thanks for your help so far.

Cheers

Interesting - the v4.5 folder does not exist on the server:

%SYSTEMROOT%\Microsoft.NET\Framework\v4.5\aspnet_regiis.exe -I

Just versions v4.0.30319 and older.

I have re-run the pre-requesites and it states no change:

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features, NET-Framework-Core, NET-HTTP-Activation, NET-Non-HTTP-Activ, NET-WCF-HTTP-Activation45

please recheck the prerequisites once again 

http://blogs.technet.com/b/dodeitte/archive/2015/05/04/installing-prerequisites-for-skype-for-business-server-2015.aspx

This is for Skype for Business - not Office Web Apps?  Should I mimic the pre-requisites?

All the troubleshooting has been on the Office Web Apps server - not the Skype for Business servers.