irizvi
asked on
We are not able to share powerpoint file on lync 2013. error"couldnt uploadxyz.ppt. Service is not available. please contact your system administrator".
We are not able to share powerpoint file on lync 2013. error"couldnt uploadxyz.ppt. Service is not available. please contact your system administrator".
We have checked .netframework . There are events related to powerpoint services on App server.
everyone is having issues. Only sharing ppt file.
Please help..
We have checked .netframework . There are events related to powerpoint services on App server.
everyone is having issues. Only sharing ppt file.
Please help..
Sharing PowerPoint requires that you set up an office web apps server. You must then use the Lync topology builder to tell Lync where the office web apps server lives. When shareung a PowerPoint deck, it is uploaded that server for sharing.
ASKER
we have a office web app server configured for it.. Only issue is with ppt sharing. Please suggest..
Ppt sharing is the only time OWAS is used. Screen sharing, application sharing and whiteboarding don't use it.nSo your problem is with the OWAS server itself or it not being listed in the topology.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So how do I fix the server or Certificate issue. I am not too familiar with Lync 2013.
you need to go to your wac server "OWA" and open iis manager ad check whether you have a valid certificate bind to the https port ..
could you also open powershell and post the result of get-officewebappfarm?
could you also open powershell and post the result of get-officewebappfarm?
ASKER
get-officewebappfarm not working..
Checked.. OWA has a valid certificate installed..
Checked.. OWA has a valid certificate installed..
Sorry I meant get-OfficeWebAppsFarm .. there's a missing S in the cmdlet.
Try again and post the result here...
please in IIS check what's the bind certificate's Friendly name. it must match the name in the result from the cmdlet that you'll use.
Try again and post the result here...
please in IIS check what's the bind certificate's Friendly name. it must match the name in the result from the cmdlet that you'll use.
ASKER
yes it was a certificate issue.