Hi I have installed a Lync 2013 Server and Office Web Apps Server. Configured Lync topology, Office Web Apps farm and certificates.
However when i start the services i get this error message in the log saying Office Web Apps discovery failed.
Connecting to the HTTPS discovery URL is working fine, and brings up the XML-page (after i click "show all content").
The two servers are located on the same internal network, DNS resolves fine both ways, and no firewall rules blocks any connections between the two. Can anyone please help me figure this out?
Only identical problem found online is here (Invalid Uri syntax for WAC configuration):
http://blogs.technet.com/b/dodeitte/archive/2012/09/10/office-web-apps-server-amp-lync-server-2013.aspx
He resolved the problem by assigning a new OAuthTokenIssuer certificate. This however did not fix the problem in my case.
Regards
Sverre A. Veel
However when i start the services i get this error message in the log saying Office Web Apps discovery failed.
"
Event ID: 41033
Description:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
Attempted Office Web Apps Server discovery Url:
Received error message: Invalid Uri syntax for WAC configuration
The number of retries: 1,
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.
I can access the OWAS server Url from Lync Server
"Connecting to the HTTPS discovery URL is working fine, and brings up the XML-page (after i click "show all content").
The two servers are located on the same internal network, DNS resolves fine both ways, and no firewall rules blocks any connections between the two. Can anyone please help me figure this out?
Only identical problem found online is here (Invalid Uri syntax for WAC configuration):
http://blogs.technet.com/b/dodeitte/archive/2012/09/10/office-web-apps-server-amp-lync-server-2013.aspx
He resolved the problem by assigning a new OAuthTokenIssuer certificate. This however did not fix the problem in my case.
Regards
Sverre A. Veel