locked
Office Web App 2013 - Office Applications are showing preview in SharePoint 2013 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    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

    Thursday, July 16, 2015 9:24 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    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?

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, July 24, 2015 7:26 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you update SharePoint or Office web apps server farm?



    Thursday, July 16, 2015 9:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Recently some patches released and restarted my OWA server. Any one is having same issue ?
    Thursday, July 16, 2015 10:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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

    Visit my blog at : www.absolute-sharepoint.com

    Friday, July 17, 2015 12:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    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).

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, July 17, 2015 12:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Vlad. I will look into these videos.
    Friday, July 17, 2015 3:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually, I tried this but no luck. :(

    Thanks,

    Rao

    Friday, July 17, 2015 3:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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 isn’t 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.

    Visit my blog at : www.absolute-sharepoint.com


    Friday, July 17, 2015 3:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

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

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

    sachin

    Friday, July 17, 2015 4:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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)


    Thursday, July 23, 2015 11:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is the Security Token Service IIS Application Pool started?

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, July 24, 2015 1:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes.
    Friday, July 24, 2015 3:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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

    Friday, July 24, 2015 7:25 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    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?

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, July 24, 2015 7:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry for the delay in responding your comment. Actually STS is working fine with all the request in the SharePoint except the Office Web App. We raised a ticket with Microsoft to look into this issue. I will update here once I get the response from MS.

    -

    Rao

    Tuesday, August 25, 2015 9:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Rao,

    I'm experiencing the same problem.

    Could you solve the problem with the support from MS?

    best regards

    Gottfried

    Friday, December 4, 2015 9:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you resolve this?
    Wednesday, July 20, 2016 1:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Rao,

    are there any news regarding this issue from your ticket to Microsoft?

    Kind regards

    T. Weeken

    Tuesday, December 13, 2016 4:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I was having the same issue on a production farm environment. 

    SOLUTION for me:

Disable Dell Change Auditor Agent Service and Restart IIS.

Seems that Dell Change Auditor may mess with your named pipes (net.pipe).
    https://blogs.msdn.microsoft.com/spses/2016/01/21/sharepoint-2013-unable-to-viewedit-office-documents-in-browser-using-office-web-apps-2013/


    BELOW ARE SOME OF THE OTHER THINGS I TRIED BEFORE COMING TO THE ABOVE SOLUTION.

    Because it wasn't working in production, I tried setting it up in a dev environment and it worked fine to my amazement.  Seeing it working in a Dev environment gave me hope.

    The  ULS logs have an entry that looks like the following regarding a WOPI web service before going to the net.pipe lines:

    WOPI endpoint after encoding: https://sp2013hv/_vti_bin/wopi.ashx 


    Then, the ULS logs show that the net.pipe connection was sent and received successfully:

    Trusted provider is missing. Provider: '00000003-0000-0ff1-ce00-000000000000'	e3ebe09d-f67b-902a-e038-a11a50f62a83
WcfSendRequest: RemoteAddress: 'net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc' Channel: 'Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract' Action: 'http://schemas.microsoft.com/sharepoint/2011/05/securitytokenservice/IApplicationSecurityTokenServiceContract/Issue' MessageId: 'urn:uuid:06d9ecfc-7eb4-4a6f-a7fd-df2957adedb0'	e3ebe09d-f67b-902a-e038-a11a50f62a83
Entering monitored scope (ExecuteWcfServerOperation). Parent No	 
WcfReceiveRequest: LocalAddress: 'net.pipe://sp2013hv/SecurityTokenServiceApplication/appsts.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/2011/05/securitytokenservice/IApplicationSecurityTokenServiceContract/Issue' MessageId: 'urn:uuid:06d9ecfc-7eb4-4a6f-a7fd-df2957adedb0'	e3ebe09d-f67b-902a-e038-a11a50f62a83


    Unfortunately, for some reason the net.pipe://localhost/SecurityTokenServiceApplication does not work in the production environment.  I also noticed there is no reference to the wopi.ashx in the ULS logs where it is not working.

    Some of the recommended troubleshooting steps I've tried to no avail:

    1) Verified that "Net.Pipe Listener Adapter" Service and "Windows Process Activation Service" were running.

    2) Verified that the service is running on the http and https interfaces by going to:

    http://localhost:32843/SecurityTokenServiceApplication/appsts.svc
    https://localhost:32844/SecurityTokenServiceApplication/appsts.svc

    3) Verified Firewalls, HIPs, and Antivirus weren't the cause by disabling them temporarily.

    4) Compared the Local Security Policies of the production vs dev server.  Made tweaks to simulate the production environment in dev, but it still worked.

    5) Granted the SecurityTokenService App pool account admin on the server.  Still didn't work.

    6) Checked Named Pipes to make sure that Named Pipes were being created using PowerShell.

    $listofPipes=[System.IO.Directory]::GetFiles("\\.\\pipe\\")

    http://stackoverflow.com/questions/258701/how-can-i-get-a-list-of-all-open-named-pipes-in-window

    7) Compared the SPSecurityTokenServiceConfigs between the dev and production servers:

    Get-SPSecuriityTokenServiceConfig

    8) Set-SPWOPIZone: Tried both internal-https and external-https

    9) Made a backup of and tweaked the C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\SecurityToken\web.config by trying to specify the endpoint location as localhost.  Turned on mex and wsdl information by setting httpGetEnabled and httpsGetEnabled to true. Added serviceDebug behavior for debug.

    Here's the original web.config for reference.  I probably expended quite a few hours looking at the configuration and looking up the possible attributes for the different behavior, endpoint, and binding settings.  In the end, none of the tweaks I made helped, so I changed them back to the original file (which I had made a copy of before making any changes).

    <?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <system.serviceModel>

    <!-- Behavior List: -->
    <behaviors>
      <serviceBehaviors>
        <behavior name="SecurityTokenServiceBehavior" >
          <!-- The serviceMetadata behavior allows one to enable metadata (endpoints, bindings, services) publishing.
               This configuration enables publishing of such data over HTTP GET.
               This does not include metadata about the STS itself such as Claim Types, Keys and other elements to establish a trust.
          -->
          <serviceMetadata httpGetEnabled="true" />
          <!-- Default WCF throttling limits are too low -->
          <serviceThrottling maxConcurrentCalls="65536" maxConcurrentSessions="65536" maxConcurrentInstances="65536" />

        </behavior>
        <behavior name="ApplicationSecurityTokenServiceBehavior" >
          <serviceMetadata httpGetEnabled="false" httpsGetEnabled="false" />
          <serviceThrottling maxConcurrentCalls="65536" maxConcurrentSessions="65536" maxConcurrentInstances="65536" />

        </behavior>
      </serviceBehaviors>
    </behaviors>

    <!-- Service List: -->
    <services>
      <service name="Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract"     
               behaviorConfiguration="SecurityTokenServiceBehavior" >
        <!-- This is the HTTP endpoint that supports clients requesing tokens. This endpoint uses the default 
             standard ws2007HttpBinding which requires that clients authenticate using their Windows credentials. -->
        <endpoint
          address=""
          binding="customBinding"
          bindingConfiguration="spStsBinding"
          contract="Microsoft.IdentityModel.Protocols.WSTrust.IWSTrust13SyncContract" />

        <!-- This is the HTTP endpoint that supports clients requesting service tokens. -->
        <endpoint
          name ="ActAs"
          address="actas"
          binding="customBinding"
          bindingConfiguration="spStsActAsBinding"
          contract="Microsoft.IdentityModel.Protocols.WSTrust.IWSTrust13SyncContract" />

        <!-- This is the HTTP endpoint that supports IMetadataExchange. -->
        <endpoint address="mex"
                  binding="mexHttpBinding"
                  contract="IMetadataExchange" />
      </service>
      <service
        name="Microsoft.SharePoint.IdentityModel.ApplicationSecurityTokenService"
        behaviorConfiguration="ApplicationSecurityTokenServiceBehavior">
        <endpoint
          name="app"
          address=""
          binding="customBinding"
          bindingConfiguration="spStsApplicationBinding"
          contract="Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract" />
      </service>
      <service name="Microsoft.SharePoint.Administration.Claims.SPWindowsTokenCacheService">
        <endpoint address=""
                  binding="customBinding"
                  bindingConfiguration="SPWindowsTokenCacheServiceHttpsBinding"
                  contract="Microsoft.SharePoint.Administration.Claims.ISPWindowsTokenCacheServiceContract" />
      </service>
    </services>

    <!-- Binding List: -->
    <bindings>
      <customBinding>
        <binding
          name="spStsBinding">
          <binaryMessageEncoding>
            <readerQuotas
              maxStringContentLength="1048576"
              maxArrayLength="2097152"/>
          </binaryMessageEncoding>
          <httpTransport
            maxReceivedMessageSize="2162688"
            authenticationScheme="Negotiate"
            useDefaultWebProxy="false" />
        </binding>
        <binding
          name="spStsActAsBinding">
          <security
            authenticationMode="SspiNegotiatedOverTransport"
            allowInsecureTransport="true"
            defaultAlgorithmSuite="Basic256Sha256"
            messageSecurityVersion="WSSecurity11WSTrust13WSSecureConversation13WSSecurityPolicy12" />
          <binaryMessageEncoding>
            <readerQuotas
              maxStringContentLength="1048576"
              maxArrayLength="2097152"/>
          </binaryMessageEncoding>
          <httpTransport
            maxReceivedMessageSize="2162688"
            authenticationScheme="Negotiate"
            useDefaultWebProxy="false"/>
        </binding>
        <binding
          name="spStsApplicationBinding">
          <binaryMessageEncoding>
            <readerQuotas
              maxStringContentLength="1048576"
              maxArrayLength="2097152" />
          </binaryMessageEncoding>
          <namedPipeTransport
            maxPendingAccepts="250"
            maxPendingConnections="250"
            maxReceivedMessageSize="2162688">
            <connectionPoolSettings
              idleTimeout="00:30:00"
              maxOutboundConnectionsPerEndpoint="250"/>
          </namedPipeTransport>
        </binding>
        <binding name="SPWindowsTokenCacheServiceHttpsBinding">
          <security
            authenticationMode="IssuedTokenOverTransport"
            defaultAlgorithmSuite="Basic256Sha256" />
          <textMessageEncoding>
            <readerQuotas maxStringContentLength="1048576" maxArrayLength="2097152"/>
          </textMessageEncoding>
          <httpsTransport maxReceivedMessageSize="2162688" authenticationScheme="Anonymous" useDefaultWebProxy="false" />
        </binding>
      </customBinding>
    </bindings>
  </system.serviceModel>

  <system.webServer>
    <security>
      <authentication>
        <anonymousAuthentication enabled="true" />
        <windowsAuthentication enabled="true">
          <providers>
            <clear />
            <add value="Negotiate" />
            <add value="NTLM" />
          </providers>
        </windowsAuthentication>
      </authentication>
    </security>
    <modules>
      <add name="WindowsAuthenticationModule" />
    </modules>
  </system.webServer>
  <system.net>
    <connectionManagement>
      <clear />
      <add address="*" maxconnection="10000" />
    </connectionManagement>
  </system.net>
</configuration>

    10) Added registry settings to disable the loop back check.

    https://support.microsoft.com/en-us/help/896861/you-receive-error-401.1-when-you-browse-a-web-site-that-uses-integrated-authentication-and-is-hosted-on-iis-5.1-or-a-later-version

    11) Did a side by side Service comparison between the two servers.

    It was then that I gave up.  I decided to write this posting to see if I could get any help from someone who may have resolved this issue.  I went home in dismay after not being able to get it working.  Not feeling like giving up totally, yet I just started googling some more on my cell phone. 

    However, rather than googling specifically for the EndPointNotFoundExceptioin on net.tcp://localhost, I googled general SharePoint and Office Web Apps issues.  It was there that I found the article regarding Dell Change Auditor.   In the side by side service comparison, I noticed the Dell Change Auditor Agent service was running on the production environment.  Didn't think anything of it, until I saw that article.

    https://blogs.msdn.microsoft.com/spses/2016/01/21/sharepoint-2013-unable-to-viewedit-office-documents-in-browser-using-office-web-apps-2013/

    Once the net.pipe issue was resolved, there was one last issue I had to solve. When attempting viewing documents with OfficeWebApps, I no longer got the "Something went wrong," but it would hang.

    In the Office Web Apps windows event log, I found entries about a certificate trust issue.  I had used *.domainname as my certificate. I discovered that you should use a simple friendly name for the certificate that you use. 

    1) The friendly name of the certificate you use for OfficeWebApps should be a simple one without * or . in it.  https://whitepages.unlimitedviz.com/2014/10/how-to-use-a-wildcard-certificate-with-office-web-apps-2013/

    2) Also, if you are having cert trust issues, be sure that the certificates involved are in the Trusted Root Authorities.  You can use the certificates mmc to do this, as well as change the friendly name.

    3) Since I was using https, I made sure that OAuthOverHttp was disabled in the Get-OfficeWebAppsFarm.  You can change the settings by using the Set-OfficeWebAppsFarm command.

    4) Once making changes, I had to restart IIS and the OfficeWebApps Service.  Once done, I finally saw the glorious document preview via Office Web Apps that I had spend so many hours trying to get.

    FINAL NOTE in case nothing works for you:

    Office Web Apps seems like a pretty cool service, but if you can't get it working, SharePoint runs perfectly fine without it.

    To unbind SharePoint from Office Web Apps run the following from SharePoint PowerShell on a WFE:

    Remove-SPWOPIBinding -All:$true





    Thursday, March 23, 2017 8:07 PM