Hi All,

In my SharePoint 2013 I am able to see the preview for ASPX pages and as well as Images. But not for Office documents (like Excel, PPT, Word). When I try to see the preview for these document it is giving 'An unexpected error has occurred.'

Note: Few days everything seems to be working. From day before yesterday things are wrong.

Any suggestion will be really appreciated.

-

Thank you,

Rao

Did you update SharePoint or Office web apps server farm?

• Edited by Bharath Kumar Arja 9 hours 44 minutes ago

Recently some patches released and restarted my OWA server. Any one is having same issue ?

Hello,

Did you do automatic patches? It's not supported for Office Web Apps.  I got a course on Pluralsight on Office Web Apps that explains how to patch them properly and you can find it here: http://www.pluralsight.com/courses/deploying-office-web-apps-2013 

Technet documentation is here: https://technet.microsoft.com/en-us/library/jj966220.aspx?f=255&MSPPError=-2147217396

Basically, with WAC patches, you have to rebuild the WAC farm every time it is patched. I'd strongly recommend you script out the creation of New-OfficeWebAppsFarm (and New-OfficeWebAppsMachine, if you have >1 WAC server).

Did you update SharePoint or Office web apps server farm?

• Edited by Bharath Kumar Arja Thursday, July 16, 2015 9:59 PM

Did you update SharePoint or Office web apps server farm?

• Edited by Bharath Kumar Arja Thursday, July 16, 2015 9:59 PM

Thanks Vlad. I will look into these videos.

Actually, I tried this but no luck. :(

Thanks,

Rao

Actually, I tried this but no luck. :(

Thanks,

Rao

Actually, I tried this but no luck. :(

Thanks,

Rao

According to Technet documentation, if you apply the updates wrong, you will not only have to remove the farm and recreate the farm, but also uninstall the bits and reinstall. Here is extract:

Applying Office Web Apps Server updates by using the automatic updates process isnt supported with Office Web Apps Server. This is because updates to an Office Web Apps Server must be applied in a specific way, as described in this article. If Office Web Apps Server updates are applied automatically, users may be unable to view or edit documents in Office Web Apps. If this happens, you have to rebuild your Office Web Apps Server farm. To rebuild a farm, you must remove the Office Web Apps Server from the farm by using Remove-OfficeWebAppsMachine, uninstall Office Web Apps Server by using Add or remove programs, and then reinstall Office Web Apps Server by following the steps that are described in Deploy Office Web Apps Server. After you have reinstalled, apply the update by following the steps that are described in this article.

According to Technet documentation, if you apply the updates wrong, you will not only have to remove the farm and recreate the farm, but also uninstall the bits and reinstall. Here is extract:

Applying Office Web Apps Server updates by using the automatic updates process isnt supported with Office Web Apps Server. This is because updates to an Office Web Apps Server must be applied in a specific way, as described in this article. If Office Web Apps Server updates are applied automatically, users may be unable to view or edit documents in Office Web Apps. If this happens, you have to rebuild your Office Web Apps Server farm. To rebuild a farm, you must remove the Office Web Apps Server from the farm by using Remove-OfficeWebAppsMachine, uninstall Office Web Apps Server by using Add or remove programs, and then reinstall Office Web Apps Server by following the steps that are described in Deploy Office Web Apps Server. After you have reinstalled, apply the update by following the steps that are described in this article.

According to Technet documentation, if you apply the updates wrong, you will not only have to remove the farm and recreate the farm, but also uninstall the bits and reinstall. Here is extract:

Applying Office Web Apps Server updates by using the automatic updates process isnt supported with Office Web Apps Server. This is because updates to an Office Web Apps Server must be applied in a specific way, as described in this article. If Office Web Apps Server updates are applied automatically, users may be unable to view or edit documents in Office Web Apps. If this happens, you have to rebuild your Office Web Apps Server farm. To rebuild a farm, you must remove the Office Web Apps Server from the farm by using Remove-OfficeWebAppsMachine, uninstall Office Web Apps Server by using Add or remove programs, and then reinstall Office Web Apps Server by following the steps that are described in Deploy Office Web Apps Server. After you have reinstalled, apply the update by following the steps that are described in this article.

Follow below link while patching office web apps server. Do not do automatic update.

https://technet.microsoft.com/en-us/library/jj966220.aspx

Follow below link while patching office web apps server. Do not do automatic update.

https://technet.microsoft.com/en-us/library/jj966220.aspx

Follow below link while patching office web apps server. Do not do automatic update.

https://technet.microsoft.com/en-us/library/jj966220.aspx

I checked the Videos those are really good. I re-configured my WAC server. Still I am facing the same issue. After doing research on the application and WAC I found that it's a problem with SharePoint Security Token. So provisioned the all the service application. After that also no use. Here is the error message I am getting in my ULS log.

Any suggestion please....

Attached the error screen shot.

 WOPIFrame - Unhandled exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening
 at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.    Server stack trace:     
 at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)    
 at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)    
 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
 at [0]:     
 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)    
 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)    
 at Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract.Issue(RequestApplicationSecurityToken request)    
 at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()    
 at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)    
 at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user, String applicationContext, DateTime& validTo)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, String proofKeyId, SPUrlZone zone, Int64& ttl)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetWOPITargetInternal(HttpContext httpContext, SPWeb web, Object& spPrimeObject, SPWOPIAction& requestedAction, SPRegionalSettings spSettings, String& wopiAppUrl, String& wopiFavIconUrl, String& wopiAccessToken, Int64& wopiAccessTokenTtl, String& errorMessageToDisplay, String& redirectUrl)    
 at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoadHelper(WOPIFrame frame)    
 at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoad(WOPIFrame frame)

• Edited by P.Venkateswara Rao 8 hours 31 minutes ago

Is the Security Token Service IIS Application Pool started?

I checked the Videos those are really good. I re-configured my WAC server. Still I am facing the same issue. After doing research on the application and WAC I found that it's a problem with SharePoint Security Token. So provisioned the all the service application. After that also no use. Here is the error message I am getting in my ULS log.

Any suggestion please....

Attached the error screen shot.

 WOPIFrame - Unhandled exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening
 at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.    Server stack trace:     
 at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)    
 at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)    
 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
 at [0]:     
 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)    
 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)    
 at Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract.Issue(RequestApplicationSecurityToken request)    
 at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()    
 at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)    
 at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user, String applicationContext, DateTime& validTo)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, String proofKeyId, SPUrlZone zone, Int64& ttl)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetWOPITargetInternal(HttpContext httpContext, SPWeb web, Object& spPrimeObject, SPWOPIAction& requestedAction, SPRegionalSettings spSettings, String& wopiAppUrl, String& wopiFavIconUrl, String& wopiAccessToken, Int64& wopiAccessTokenTtl, String& errorMessageToDisplay, String& redirectUrl)    
 at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoadHelper(WOPIFrame frame)    
 at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoad(WOPIFrame frame)

• Edited by P.Venkateswara Rao Thursday, July 23, 2015 11:08 PM

Yes.

Vlad,

Actually, my admin team configured 2 WAC servers recently for Lync. These WAC servers are working fine with Lync. I thought to connect my SharePoint server to this WAC and did the same. But I am getting the same issue. So I checked the log files and I found the error in my ULS logs. Tried different ways to solve this but no luck. Any idea on the below error please ?

WOPIFrame - Unhandled exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening
 at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.    Server stack trace:     
 at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)    
 at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)    
 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)    
 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
 at [0]:     
 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)    
 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)    
 at Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract.Issue(RequestApplicationSecurityToken request)    
 at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()    
 at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)    
 at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo)    
 at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user, String applicationContext, DateTime& validTo)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, String proofKeyId, SPUrlZone zone, Int64& ttl)    
 at Microsoft.SharePoint.Utilities.SPWOPIHost.GetWOPITargetInternal(HttpContext httpContext, SPWeb web, Object& spPrimeObject, SPWOPIAction& requestedAction, SPRegionalSettings spSettings, String& wopiAppUrl, String& wopiFavIconUrl, String& wopiAccessToken, Int64& wopiAccessTokenTtl, String& errorMessageToDisplay, String& redirectUrl)    
 at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoadHelper(WOPIFrame frame)    
 at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoad(WOPIFrame frame)

-

Thanks,

Rao

That issue is on the SharePoint side. Again, looks like the STS isn't responding to requests. Do you see the same type of issue (STS non-responsive) when monitoring the ULS in real time while users are browsing sites on the server?