Office Web Apps Error after SP 2013 September 2014 CU

Hello  Everyone,
I have a single front end and single SQL server for my SharePoint 2013 deployment.  I also have Office Web Apps setup and running.  However after installing SP 1 and the latest September 2014 CU it appears our users are seeing the below prompt
when open a Word doc in Office Web Apps.
However I am finding that if they use IE 9 or 10 and even Firefox everything works normal.  This appears to be affecting just Word.
As for my Office Web Apps server it is still at Version 15.0.4420.1017 (RTM) 
If I need to update my Office Web Apps server what order should i do.  SP1, July, then Sept?  
Thanks,
Ian...

You need to apply office web app update. 
It should be in below order.
Office web app Sp1
September 2014 update
If this helped you resolve your issue, please mark it Answered

Similar Messages

  • Office Web Apps server / Lync server 2013

    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.
    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

    Hi,
    In addition, please make sure you have restarted front end and office web apps server after reissuing the certificate.
    Kent Huang
    TechNet Community Support

  • Office web apps Server for Sharepoint 2013

    Hello,
    I used the following article to install office web apps server and hook it up to a test sharepoint server:
    http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx. The OWAS service was verified as working by loading:
    https://owas.companyname.com/hosting/discovery
    For the sharepoint configuration phase, the following commands were run on the sharepoint machine:
    1) New-SPWOPIBinding -ServerName "owas.companyname.com"   -- (owas.companyname.com) is the host name of the owas server)
    2) Get-SPWOPIZone
    3) Set-SPWOPIZone -zone "external-https"
    However, office documents are still launching in the desktop office applications, not in the browser. Any ideas of what else I may need to do?
    thanks,
    Sherazad

    Hi  ,
    According to your description, my understanding is that you fail to configure Office Web Apps for your SharePoint 2013.
    How about run Get-SPWOPIZone? If you can get a result, it says that your  SharePoint  have connected with Office Web Apps.
    Then you can run below command to  change the zone to internal-https.
    Set-SPWOPIZone -zone "internal-https"
    Reference:
    http://technet.microsoft.com/en-us/library/ff431687(v=office.15).aspx 
    http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
    contact [email protected]
    Eric Tao
    TechNet Community Support

  • SharePoint 2013 and MS Office Web Apps - error in sharepoint's url calls OWAps

    I have new SharePoint 2013 Server farm and one dedicated Office Web Apps (OWAps) server.
    This farm is placed in one domain (Acompany.local). There is other domain BCompany.local whitch has both trusted to first domain (two diffirent forests, two company's branches).
    Users from second domain BCompany.local well see intranet portal, build in sharepoint in the first domain (url like http://intranet.Acompany.local).
    But, when they try to use OWAps, f.e. whatching preview or try to open docs for edit in browser - they see error in frame.
    I'm looked it in google chrome's developer tools and find' that sharepoint use wrong url to call OWAps - like http://owaps/... instead of http://owaps.Acompany.local/...
    When I created new office web app farm by:
    New-OfficeWebAppsFarm -InternalURL "http://owaps.Acompany.local" - ExternalURL "http://owaps.Acompany.local" -AllowHttp -EditingEnabled
    And in sharepoint farm new SWOPI binding by:
    New-SPWOPIBinding -ServerName "http://owaps.Acompany.local" -AllowHTTP
    Get-SPWOPIBinding tell that all SWOPI bindings are http://owaps.Acompany.local, but in devtools I continue to see wrong http://owaps/... url
    Any idea to fix this behavior?

    The reason WAC is recommended to be installed on a dedicated server is that it recreates the IIS sites/settings. This is why you're seeing the setting reset itself after restart.
    What I'd probably recommend is creating a script that queries the WAC URL on a regular basis.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Office Web App error - unable to open PDF after multiple trials

    Hi, we are using Office Web App server 2013 on win server 2012 (NO Sharepoint installed) to preview files (doc, docx, pdf, xls, xlsx, ppt, pptx), OWA is set as http, wopihost
    is http as well under different from HTTP80, HTTP809 application pool
    File conversion if fine for small files and large files to some point - we can process same large pdf (100MB) 30-50 times, but after that there is a message
    "Sorry, Word Web App ran into
    a problem opening this document. To view this document please open it in Microsoft Word."
    Server has plenty of free space, PerfMon
    does not show spikes, no memory spikes in Process Manager. ULS logs do not provide any good info either...
    No errors in event log under Applications,
    System, or Microsoft Office Web Apps sections.
    That error will be shown if we process
    the same file. if try to process different file it works fine (again - few dozen times), but if after that I try to process first file - it shows error again.
    Documents
    are located on the same server as OWA installed, same machine has wopi site in non owa application pool (from Microsoft demo
    - C#)
    The only resolution i found is to reset
    WAC server from PowerShell or restart IIS - after that it starts to process original file...
    If I just recycle OWA application pools
    - HTTP80, HTTP809 it does not help. (tried to change Recycling condition in IIS for those pools - it slightly improves situation but does not resolve).
    I can reproduce such pattern with different file types, it just matter of number of hits.
    Same error present if we use OWA and wopi on machine as https with certificate.
    We use VerboseEx option for logging - no errors in ULS log files, but multiple Sync exiting
    early records similar to 
    Sync exiting early: LastSyncTime = 09/16/2014 14:52:07    
     at Microsoft.Office.Web.Apps.Environment.WacServer.ACacheableFarmStateObject.Sync(Boolean force)  
     at Microsoft.Office.Web.Apps.Environment.WacServer.AFarmSettings.TryGetSettingValue[T](String settingName,
    T& value, Boolean shouldProcessValue)    
     at Microsoft.Office.Web.Apps.Environment.WacServer.WSConfigAdapter.TryGetValue[T](String settingName,
    T& value)    
     at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.GetAgentUri(WebAgentProperties
    agentProperties, String machineName, String fqdn)    
     at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.UpdateServiceList()
     at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.FindAllServiceInstances()
     at Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state)    
     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
    callback, Object state, Boolean preserveSyncCtx)    
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback,
    Object state, Boolean preserveSyncCtx)    
     at System.Threading.TimerQueueTimer.CallCallback()    
     at System.Threading.TimerQueueTimer.Fire()    
     at System.Threading.TimerQueue.FireNextTimers()  
    ---------------------------------There are some paired records
    Cached service list has 39 service instances before the update
    Cached service lists has 39 service instances after the update
    So it goes as follows: OWA processing all formats fine, after trying same 100mb pdf file 50 times (it is possible to get same error with docx, just bigger number of trials) it does not process that pdf file, but processes others.
    After IIS reset it works as usual again. After trying another 100mb pdf file 50-60 times OWA stops to process that another file... We are expecting large number of hits and resetting IIS every 30min is not a good solution...
    Any help will be appreciated.
    Thank you

    Hi ,
    Thank you for your post.
    Whether the issue occurs with different file types or only the PDF.
    Based on your description, when you reset WAC server from PowerShell or restart IIS, the issue is solved temporarily.
    I recommend that you check the application account, re-enter the account, then reset the IIS.
    whether the issue occurs with different file types or only the PDF.
    In addition, please check if the link is useful:
    http://stevemannspath.blogspot.jp/2013/04/sharepoint-2013-pdf-support-and.html
    Best Regards,  
    Lisa Chen

  • Office Web Apps Error

    hi -
    I have Office Web Apps 2013 installed and configured on my dev server.  It's set to allow HTTP.
    When I try to preview a Word document, the frame displays the following message:
    This content cannot be displayed in a frame. 
    To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.
    According to this
    link, low memory conditions can cause this error in the preview.  I have checked that and we are OK with memory.
    For Excel documents, I get the following error in preview:
    The website cannot display the page
    Most likely causes:
    •The website is under maintenance.
    •The website has a programming error.

    HI,Seems to be issue with the connection between sharepoint and office webapp.Check the below URL to get the connection successed and work succesfully.
    http://expertsharepoint.blogspot.de/2013/12/microsoft-office-web-apps-server-2013_19.html
    Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

  • Office Web App error in extended web application

    I have a web application that has been extended in intranet zone. While all feature works in the application in the default zone of office web app, creating new document from site it self does not work in intranet zone. Error I am getting is sorry, there
    was a problem and we can't open this document. If this happens again, try opening document in microsoft word. I was not able to find anything regarding this.
    My extended web application is using FBA and default zone uses windows. 
    Thanks,
    Errors in ULS logs
    WOPI ProcessRequest - Unhandled Exception in WOPI app layer  [e: System.InvalidOperationException: Operation is not valid due to the current state of the object.    
     at Microsoft.SharePoint.SPUserToken.GetClaimsUserLoginName()    
     at Microsoft.SharePoint.IdentityModel.SPIdentityContext.Create(SPUserToken token, Boolean isShareByLinkGuestUser)    
     at Microsoft.SharePoint.IdentityModel.SPIdentityContext.Create(SPUser user)    
     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, WopiTokenContext tokenContext, Int64& ttl)    
     at Microsoft.SharePoint.SoapServer.Wopi.RunCobalt(HttpContext context, CommonRequestData requestData, CommonResponseData responseData)    
     at Microsoft.SharePoint.SoapServer.Wopi.ProcessRequestCore(HttpContext context, CommonRequestData requestData, CommonResponseData responseData)]
    WOPI - CopyRequestBodyToStream throw exception [exception System.ObjectDisposedException: Cannot access a disposed object.  Object name: 'Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedMemoryStream'.    
     at Microsoft.SharePoint.Utilities.SPChunkedStream.get_Length()    
     at Microsoft.SharePoint.SoapServer.Wopi.CopyRequestBodyToStream(HttpContext context)]
    WOPI cobalt - Failed to read entire request body, url
    sachin

    Hi sachin,
    According to your description, my understanding is that you got an error when you created a new document using OWA in the extended zone with FBA.
    The issue stems from SharePoint and is due to an error in the access token generation when a user tries to load a document in the Office Web Apps.
    The current workaround is to configure FBA authentication in the Default zone of the effected web application.
    More information, please refer to the link:
    http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2014/03/20/office-web-apps-2013-errors-previewing-viewing-editing-documents-when-using-fba-in-the-extended-zone-but-not-the-default-zone.aspx
    I hope this helps.
    Thanks,
    Wendy
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Wendy Li
    TechNet Community Support

  • Installation - Office Web Apps Server on SharePoint 2013 Foundation - Download missing

    Hi all,
    I'm trying to download Office Web Apps Server.
    As of November 24th, the download was relocated on the Volume Licencing Center (as per this
    link ).
    Connected to VLCS, I'm trying to find the download from the tree / using filter..... I'm not finding anything.
    Was the product renamed / not available at this time ?
    Thx

    Are you aware of the type of subscription needed to download it?
    The client I work for is a government department....  I think they have quite a big subscription!
    Thx.
    Update
    I just found a great link to the list of products available thru the Volume Licensing Program
    (http://www.microsoft.com/licensing/products/products.aspx#tab=2).
    Office Web Apps Server requires an Office 2013 Licence.... We are checking this requirement right now...

  • Office Web App error

    I have setup my Office Web App Environment following the following article. 
    http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
    This is a production environment with HTTPS.  I can go to
    https://URL/hosting/discovery  and it pulls up the XML like it should.
    The setup seemed to go well but when I try to open the docs up from SharePoint I get he following errors.
    When opening a Word Doc: "Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word"
    When opening a PowerPoint Doc: "Sorry, we couldn't open this presentation because we ran into a problem. Please try again."
    When opening a Excel Doc: "We couldn't find the file you wanted. It's possible the file was renamed, moved or deleted."
    I see suggestions for AllowOAthOverHttp but did not set this because it is HTTP.  I also have the zone set to external-HTTPS.
    Please let me know if you have any suggestions.
    Thank you,

    Try to restart IIS. Then check if your domain
    is is allowed to connect with office web apps server by running Get-OfficeWebAppsHost
    cmdlet.
    If your domain is not the the allowed list, add it by New-OfficeWebAppsHost -Domain <String>.

  • Office web app error for one note only

    There is strange error in my SharePoint 2013 farm with OWA. Everything works fine except for one note.
    If you click in the notebook on the left hand side of the site, for first time everything works fine. When you try to click the same link second time, either server error comes up in chrome and nothing in IE. If i deactivate the web feature one note and
    reactivate it, it works again for first time and nothing comes up for the second time. Error i see is 
    WOPIFrame -Unhandled exception: System.TimeoutException: The open operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The read
    from the pipe did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.    
    Has anyone seen this behavior? 
    sachin

    Hi,
    According to your description, I think this issue is more related to SharePoint, I suggest that you could post it to
    SharePoint forum.
    Regards
    Starain
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Office Web Apps 2013 + could not establish trust relationship

    We currently have a three tier SharePoint 2013 Farm:
    1. Web Front End Server (Server 2008 R2 Enterprise) - Servername: TEST2SP013.domain.dom
    2. Central Admin Server (Server 2008 R2 Enterprise) - Servername: TEST2SPCA013.domain.dom
    3. SQL Server (Server 2012 Datacenter) - Servername: TESTSQL012.domain.dom
    All Machines are in the same IP/Subnet.
    We are trying to setup a new server (Server 2012 R2 Datacenter) (Servername: TEST022.domain.dom) to run Office Web Apps 2013 in our TEST environment to test the system before rolling in production and have had issues throughout the entire process.
    The technet articles we have used are:
    http://technet.microsoft.com/en-us/library/jj219435.aspx
    http://technet.microsoft.com/en-us/library/ff431687.aspx
    http://technet.microsoft.com/en-us/library/jj219627.aspx
    We finally have what I thought was a correct setup but anytime we try to edit or view a word, excel, powerpoint document within SharePoint 2013, we receive "Sorry, there was a problem and we can't open this document. If this happens again, try opening
    the document in Microsoft Word."
    We found a few How-To Setup Office Web Apps sites where other people provided step-by step instructions:
    blogs.msdn.com/b/sowmyancs/archive/2012/10/29/install-configure-amp-monitor-office-web-apps-2013-for-sp-2013.aspx
    http://www.wictorwilen.se/office-web-apps-2013-securing-your-wac-farm
    http://blogs.technet.com/b/justin_gao/archive/2013/06/30/configuring-office-web-apps-server-communication-using-https.aspx
    We reviewed the ULS logs and found the following error:
    02/14/2014 13:38:40.24  w3wp.exe (0x1C04)                        0x1BB4 Office Web Apps              
     WAC Hosting Interaction        adhsk Unexpected WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.UnexpectedErrorException: HttpRequest failed ---> Microsoft.Office.Web.Apps.Common.HttpRequestAsyncException:
    No Response in WebException ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate
    is invalid according to the validation procedure.     at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)     at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)     --- End of
    inner exception stack trace ---     at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)     at Microsoft.Office.Web.Apps.Common.Ht... 7bed0d51-511d-4541-a059-e2f72942e617
    None of the article provide specific step-by-step instructions with using HTTPS in a test environment specifically when it comes to Self-Signed Certs through Active Directory Certificate Services.
    We tried creating a Self-Signed Cert through IIS on the Office Web Apps Box which did not work.
    We tried creating a Cert through Active Directory Certificate Services which did not work.
    We tried adding the Cert through Central Admin > Security > Manage Trust which did not help.
    We verified "get-spwopizone" is set to internal-https
    We can access the Web Apps https://test022/hosting/discovery site and view the XML with no issue on any machine on our network.
    We added our domain to the list of approved domains that can use Office Web Apps as well as add "Domain Users" as the security group that can "EDIT" Office Documents through Office Web Apps. 
    After each step, we tried performing either a system reboot or IIS Reset on the Office Web Appcs and WFE box.
    My Question is how do we generate a certificate (either self-signed through IIS on the Office Web Apps Box or through AD) that will allow this application to work? I read that the Fully Qualified Domain Name needs to be in the SAN field of the Cert but when
    we request it, I have no way of entering this information. I tried following http://technet.microsoft.com/en-us/library/ff625722 to manually request a certificate with a Custom SAN but that did not work either.
    I am assuming the certificate issue is with the New Office Web Apps box. Is this correct?
    -Chris

    If internal cert then you will have to add certificate from OWA to tursted certificates in each sharepoint server plus add the certificate from central admin in Sharepoint through manage trust. Also you will need to install p7b file (file that contains
    path to root certificate to verify each intermediate certificate) for internal cert to each sharepoint server to not get certificate error.
    sachin

  • SharePoint 2013 - Office web apps intermittent issue

    From past few weeks we are seeing issue while opening the documents from sites error message says “Sorry something went wrong + An unexpected error occur on the Server”.  This happens with individual users accounts(Since it is
    expected behavior with Service account for Office web Apps). After identifying on which server we are seeing the issue we are performing the
    IIS reset on that effected Server and then issue will resolve but after a week or 10 days this is repeated again.    If anyone has seen this issue in(SP2013+OWA) please share your inputs for permanent fix.
    Subhash

    Hi Cristian,
    Below is the Log file. Please refer.
    08/06/2014 11:41:09.73 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache air4a Monitorable Token Cache: Failed to get token from distributed cache for '0).w|s-1-5-21-2146773085-903363285-719344707-1611799'.(This
    is expected during the process warm up or if data cache Initialization is getting done by some other thread). ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.73 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache air4b Monitorable Token Cache: Reverting to local cache to get the token for '0).w|s-1-5-21-2146773085-903363285-719344707-1611799'. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Application Authentication aiv3c Exception System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract],
    cannot be used for communication because it is in the Faulted state.     at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed()     at System.ServiceModel.ChannelFactory.EnsureOpened()    
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel()     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)
    StackTrace:  at onetnative.dll: (sig=6aba1f5f-ccc4-4590-af00-b8ffe7fe99a0|2|onetnative.pdb, offset=28BE6) at onetnative.dll: (offset=152A9) ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Unified Logging Service c91s Monitorable Watson bucket parameters: Microsoft SharePoint Foundation 4, ULSException14, 269cd32d "sharepoint foundation",
    0f001144 "15.0.4420.0", b2c61fc4 "system.servicemodel", 0400766f "4.0.30319.0", 51d7762b "fri jul 05 18:43:07 2013", 000000e4 "000000e4", 00000063 "00000063", 96a3e724 "communicationobjectfaultedexception",
    00215742 "aiv3c" ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Application Authentication agmxo Exception System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract],
    cannot be used for communication because it is in the Faulted state.     at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed()     at System.ServiceModel.ChannelFactory.EnsureOpened()    
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel()     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) StackTrace:  at onetnative.dll: (sig=6aba1f5f-ccc4-4590-af00-b8ffe7fe99a0|2|onetnative.pdb, offset=28BE6) at onetnative.dll: (offset=152A9) ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Unified Logging Service c91s Monitorable Watson bucket parameters: Microsoft SharePoint Foundation 4, ULSException14, 269cd32d "sharepoint foundation",
    0f001144 "15.0.4420.0", b2c61fc4 "system.servicemodel", 0400766f "4.0.30319.0", 51d7762b "fri jul 05 18:43:07 2013", 000000e4 "000000e4", 00000063 "00000063", 96a3e724 "communicationobjectfaultedexception",
    0018c5ce "agmxo" ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation WOPI ajc39 Unexpected WOPIFrame - Unhandled exception: System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract],
    cannot be used for communication because it is in the Faulted state.     at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed()     at System.ServiceModel.ChannelFactory.EnsureOpened()    
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel()     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) ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation General aat87 Monitorable An error has occurred on the server. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache'
    - Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache: Documents/Srikanth_excel test.xlsx&action=default ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:19.97 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:19.97 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedLogonTokenCache'
    - Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:19.97 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache air4g Monitorable Token Cache: Failed to initialize SPDistributedSecurityTokenCache  Exception: 'System.InvalidOperationException:
    SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()     at Microsoft.SharePoint.DistributedCaching.SPDistributedCache..ctor(String
    name, TimeSpan timeToLive, SPDistributedCacheContainerType containerType, Boolean encryptData)     at Microsoft.SharePoint.IdentityModel.SPDistributedSecurityTokenCache..ctor(String name, TimeSpan timeToLive, SPDistributedCacheContainerType
    containerType, Boolean encrptyData, TimeSpan minimumTokenExpirationWindow)     at Microsoft.SharePoint.IdentityModel.SPDistributedSecurityTokenCacheInitializer.Init(Object state)'. ccecab9c-73c6-e096-b4ac-251e2bb15206

  • Error word web app can not open this document for viewing in office web apps 2010

    Hi 
    i am receiving office web apps error.
    i installed sharepoint 2010 on windows server 2012 datacenter,
    and installed office web apps 2010 and sp2
    adil

    Hi Adil,
    From the error message, I recommend to check the things below:
    Check if Word Viewing service is started in Central Administration. If it is started, stop and re-start it.
    Check if the Word Viewing service proxy is created.
    Check if the Word Viewing service proxy is associated with web application with issue.
    If above cannot work, please check the ULS log for further research.
    More reference:
    https://amalhashim.wordpress.com/2013/01/29/sharepoint-word-web-app-cannot-open-this-document-for-viewing-because-of-an-unexpected-error/
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Using Office Web Apps Server with SharePoint Foundation 2013

    I want to know whether I can configure Office Web Apps server to edit Excel documents on a SharePoint Foundation 2013 site.
    I came across a TechNet article that states that "When used together with SharePoint Server 2013, Office Web Apps Server provides updated versions of Word Web App, Excel Web App, PowerPoint Web App, and OneNote Web App".
    However, later in the same article, it states "If your organization licenses Office 2013 through a Volume Licensing program, you can enable Office Web Apps editing for SharePoint 2013 on-premises" (without mentioning Foundation or Server).

    Hi Lemesnil,
    The Office Web App server should support the Edit licenses for SharePoin Foundation 2013, Office Web App is free to
    download, you can also try installing and configuring in a test environment, see more from the below article applied to SharePoint Foundation 2013.
    http://support.microsoft.com/kb/2886404/en-us
    http://blogs.technet.com/b/speschka/archive/2012/12/31/enabling-licensing-and-editing-for-office-web-apps-in-sharepoint-2013.aspx
    Anohter useful article aobut how to license Office Web App server, you can take a look.
    http://blogs.technet.com/b/volume-licensing/archive/2013/05/22/how-to-license-office-web-apps-server.aspx
    Thanks
    Daniel Yang
    TechNet Community Support

  • Using office web apps with SharePoint 2013

    Hi,
    I would like to use office web apps in our SharePoint 2013 environment. I would like to know if OWA has to have a dedicated server or can I install it on the SharePoint 2013 app server.
    Sherazad

    With SharePoint 2013, Office Web Apps cannot be installed on the SharePoint Server, it must be installed on its own server, not shared with any other IIS-based service (it essentially "takes over" IIS).
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Maybe you are looking for