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

Similar Messages

SharePoint 2013 Office Web App issue

We met an issue on Office Web App with SharePoint 2013.
Error message on the page:
Sorry, there was a problem and we can't open this document. If this happens again, try opening the Microsoft Word.
There is no related log in Windows Event viewer.
In SharePoint ULS log, related message as below:
08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Claims Authentication ahds8 Unexpected SPJsonWebSecurityBaseTokenHandler: Issuer name in token '00000003-0000-0ff1-ce00-000000000000@testrealm' doesn't match any of the registered issuer names for trusted sts 'collaboration metadata'. 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Application Authentication Pipeline). Execution Time=7,5254676222816 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Application Authentication ajezu Unexpected SPApplicationAuthenticationModule: Failed to authenticate request, unknown error. Exception details: System.IdentityModel.Tokens.SecurityTokenException: Issuer name is not registered at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateTokenIssuer(X509SecurityToken signingKey, String tokenIssuer) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.TryExtractAndValidateToken(HttpContext httpContext, SPIncomingTokenContext& tokenContext) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIC... 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49* w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Application Authentication ajezu Unexpected ...laimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpContext, SPFederationAuthenticationModule fam) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.AuthenticateRequest(Object sender, EventArgs e) 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation General 8nca Medium Application error when access /sites/111/_vti_bin/wopi.ashx, Error=Issuer name is not registered at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateTokenIssuer(X509SecurityToken signingKey, String tokenIssuer) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.TryExtractAndValidateToken(HttpContext httpContext, SPIncomingTokenContext& tokenContext) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIClaimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpCont... 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
The farm is having 2 WFE. There is NLB setting up for them.
AAM has been set to Default.
OWA binding set to -AllowHttp, zone set to internal-http. AllowOAuthOverHttp set to true.
The strange thing is when days ago we finish the installation, we try the link http://{server_name}/somefolder/document.docx to do the test, it works fine.
But today we try the link http://{NLB_link}/somefolder/documnet.docx, above error occur.
We are not sure whether AAM setting cause this issue or some other reaone. But even we remove the AAM to use the Server Name in link, still above issue.
Any idea/comments would be appriciated.

What is the default AAM? Is it the server_name, or the NLB_Link? Might want to try having the NLB_Link as the primary (default) AAM if you haven't already?
Not sure if you have seen the Troubleshooting steps here:
http://technet.microsoft.com/en-us/library/ff431687(v=office.15).aspx#tshoot
it discusses use of the PowerShell command:
New-OfficeWebAppHost (http://technet.microsoft.com/en-us/library/jj219459(v=office.15).aspx) which might be required for your NLB_Link.
Gavin.

SharePoint 2013 - Office Web Apps - Internal and External Use

I have successfully installed SharePoint 2013 and Office Web Apps on Azure VMs inside an Azure Virtual Network (IaaS model). Everyting is working well. However, my testing has shown that external users and internal users can't use Office Web Apps at the
same time.
Office Web Apps, installed on its own vm, accomodates an external and internal URL quite well. However, SharePoint 2013 appears to only allow one setting for WOPI Zone, either internal or external but not both. I've set the WOPI zone to Internal-HTTPS (Set-SPWOPIZone
–Zone “internal-https”). OWA works just fine if accessed from inside the Azure Virtual Network. However, if I try to access from outside the Virtual Network, from the Internet, Office Web Apps fails. The exact oppisite is also true. I can set WOPI Zone to
External-HTTPS and accessing from the Internet works fine, but accessing inside the Virtual Network fails.
Am I missing something? I, obviously, want Office Webs Apps to function properly for both internal and external users simultaneously.
I appreciate any help anyone can provide here.
Glenn

Hi Glenn,
To have both the use of Internet and Internal available to your end-users, you first need to configure AAM setting. Open Central Administration > Application Management > Configure alternate access mappings. Let's say there is an existing web application
named http://sharepoint and my end-users from local network are able to access it using the URL http://sharepoint (root site collection). Here you need to add the Internet URL by select the web application and click Edit Public URLs. Add the Internet domain
to the web application, e.g http://sharepoint.abc.com. You don't necessarily have to edit binding setting in IIS. Before continuing next steps, make sure you are able to access http://sharepoint.abc.com from the Internet while being able to access http://sharepoint
from local network (aka Internal).
On the machine where Office Web App (OWA) Server 2013 is installed, open PowerShell to add OWA module and use the following command to re-create a new OWA server farm if you've completed configuring it previously.
New-OfficeWebAppsFarm -InternalUrl "http://owa" -ExternalUrl "http://owa.abc.com" -EditingEnabled.
In this case, I'm not using SSL certificate to encrypt data over the Internet. You can use Internet-public IP of the OWA server like -ExternalUrl "http://198.xxx.xxx.xx". Add CertifcateName parameter if you want to use whether CA-issued certificate
or self-signed certificate.
On your SharePoint machine, you need to re-bind all WFE machines to WAC farm using the cmdlet New-SPWOPIBinding. Next, you need to set the WOPI zone for both internal and external.
Set-SPWOPIZone -zone "external-http"
Note: I'm not all using certificate in my guidance. But the steps to have it configured is just to add more parameter.
I've recently successfully deployed OWA multi-server farm for both internal and internet uses for two big clients. In real-world scenario, ideally OWA should be published through firewall (Forefront UAG, TMG, F5...etc). Please let me know if you still have
issues after following my steps. My email: [email protected]
Regards,
-T.s
Thuan Soldier
A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
SharePoint Vietnam |
Blog | Twitter

Sharepoitn 2013 - Office Web Apps Licensing

Dears,
I do have the license key with me for the office web apps 2013. The office web apps are working with our SharePoint 2013 portal without any issues. We were able to view the documents but couldn't edit the documents which are hosted in our portal.
How can i apply the license key for office web apps? do i need to execute any power shell commands? please advice.
thanks in advance,
Ammar

thanks Steven for your reply and appreciate the same.
but i need to know where exactly i should pass the licensing value as a parameter or the exact way to apply the license.
when i was searching i found the below link:
http://blogs.msdn.com/b/microsoft_press/archive/2013/02/04/from-the-mvps-installing-office-web-apps.aspx
under licensing it was mentioned like below:
Licensing
So the Office web apps farm is up and running and you have enabled editing. There is though another step before your users will be able to actually edit documents with Office Web Apps; you need to license the users for editing.
This is achieved by running a series of PowerShell commands on the SharePoint 2013 Central Administration server:
Get-SPUserLicense
$x = New-SPUserLicenseMapping -SecurityGroup <ADsecuritygroup> –License OfficeWebAppsEdit
$x | Add-SPUserLicenseMapping
Enable-SPUserLicensing
Is that correct? is anyone executed the above command?
please advice.
thanks in advance,
Ammar

Office web apps crome issue

I have SharePoint 2013 integrated with office web apps. I have activated the feature Open Documents in Client Applications by Default.
If I open word document in Internet explorer it opens in client application but if I open same word document in crome it open in office web apps.

Hi Harpal,
which IE you are using ? are you using IE 64 bit version ?
if yes, try opening documents in IE 32 bit.
Let us know your results, thanks
Regards,
Pratik Vyas | SharePoint Consultant |
http://sharepointpratik.blogspot.com
Posting is provided AS IS with no warranties, and confers no rights
Please remember to click Mark As Answer if a post solves your problem or
Vote As Helpful if it was useful.

Office Web Apps Server 2013 issue

Dear All,
I am encounter problem when I try to open document from my browser. Prompt message will pop-out when it try to preview a document:
"sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft word"
When I check in Event viewer, there is an error display:
"Could not contact WOPI End Point. Error details - 'Unauthorized url - http:bla.bla.bla....."
Kindly advise on how should I resolve this issue.
Application Note:
1. Windows OS: Windows Server 2012 R2
2. Office Web Server 2012 SP1
3. SharePoint Server 2013
Thank you.

Verify if you have configured correctly by checking the following post
https://technet.microsoft.com/en-us/library/ff431687.aspx
In case everything is correct, Please check the following post for similar issue
https://social.technet.microsoft.com/Forums/sharepoint/en-US/f7be5f88-8c98-464e-8596-60956b5e98fd/sharepoint-2013-office-web-apps-problem-unable-to-openviewedit?forum=sharepointgeneral.
http://blogs.technet.com/b/justin_gao/archive/2014/12/19/troubleshooting-error-event-id-8115-when-you-install-office-web-apps-server-2013-on-windows-server-2012-r2.aspx
Note:Check with non Farmadmin account
Please Mark it as answer if this reply helps you in resolving the issue,It will help other users facing similar problem

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.

Office Web Apps Issue - "Sorry, something went wrong" message when opening a document (any MS docx,ppt etc) in IE. With Chrome, it pops (Microsoft Office needs your permission) message and on RUN, it opens the document.

When opening any Microsoft documents ( docx, ppt etc) in SharePoint 2013,
Internet Explorer behavior : "Sorry, something went wrong" An unexpected error has occurred message and then nothing happens.
In Chrome : Pops (Microsoft Office needs your permission) message and on clicking RUN, it opens the document.
In Firefox : the documents opens, after asking which application do you want to use to open it.
The feature (Open Documents in Client Applications by Default) is not activate.
Why the MS documents are not working in IE 10?

Hi,
According to your post, my understanding is that you failed to open Microsoft documents in SharePoint 2013.
I recommend to Run the following PowerShell in OWA Server :
Remove-OfficeWebAppsHost # To Remove any restriction
Or
New-OfficeWebAppsHost -Domain <String> # To allow specific domain Name
In addition, you can allow OAuth via HTTP using the following commands:
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()
Here are two similar articles for you to take a look at:
http://blogs.msdn.com/b/fabdulwahab/archive/2013/10/30/office-web-apps-with-sharepoint-2013-issues.aspx
http://stevemannspath.blogspot.in/2013/03/sharepoint-2013-office-web-apps-issue.html
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Office web apps "Server error in '/wv' Application"

Hi, I successfully installed office web app for sharepoint 2013. However, when I tried to open documents, it shows the preview but once view/edit in browser, I got this error. What seems to be the problem?
Server error in '/wv' Application.
Unable to determine zone from request

Hi ,
According to your description, my understanding is that you encountered the error “Server error in '/wv' Application. Unable to determine zone from request” when you open document using Office Web Apps.
Are you using https:// to access the Office Web Apps server? Is the default zone of your web application in Alternate Access Mappings using http:// ?
If so, you can change the default zone
of your web application in Alternate Access Mappings to use https:// .
Or set AllowOAuthOverHttp to true:
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()
Reference:
http://social.technet.microsoft.com/Forums/office/en-US/de49617c-4b0a-4aa9-9877-8f085f48abc2/sharepoint-2013-sp1-and-office-web-apps-sp1-not-working-using-http?forum=sharepointadmin
http://social.technet.microsoft.com/Forums/sharepoint/en-US/f7be5f88-8c98-464e-8596-60956b5e98fd/sharepoint-2013-office-web-apps-problem-unable-to-openviewedit?forum=sharepointgeneral
Best Regards,
Eric
Eric Tao
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

Exchange and Office Web Apps Integration - Wrong Url to Outlook Web App port 444

Hi,
I'm trying to setup Office Web Apps integration with Exchange 2013. Office Web Apps are working fine with SharePoint 2013 and the WAC servers are listed as in a healthy state.
When trying to open an office document from OWA I get the usual "Sorry...we ran into a problem. Please try again"
However I have noticed that the URL that OWA is passing WAC is in the format: https://exchangeservername.domain.com:444/owa/[email protected]/wopi/files...
This is the backend server address! All the internal and external urls for owa, ecp, ews etc are set to https://mail.domain.com and they all seem to be working fine. Client Access and Mailbox roles are on the same server.
If I change the url to https://mail.domain.com/owa/[email protected]/wopi/files... then the office file opens correctly in Office Web Apps
How do I correct the URL that OWA is sending Office Web Apps?
Thanks!

Hi DJL,
If everything works well except open document via OWA, it seems Exchange server 2013 has been configured correctly.
Please follow me to check Office Web Apps Server settings and Integration.
OWAS settings
1. Certificate:
Come from a trusted CA, include FQDN of OWAS farm in SAN field.
Exportable private key.
Friendly name must be unique within Trusted Root Certificate Authorities store.
2. Farm:
New-OfficeWebAppsFarm with following parameters
-InternalURL is the FQDN of the server that runs OWAS
-ExternalURL is the FQDN so that OWAS can be access on the Internet
-CertificateName is the friendly name of the certificate to be used for HTTPS
3. Explore this URL https://mail.domain.com/hosting/discovery
If OWAS works well, you can see a WOPI-discovery XML file in web browser.
Integration
1. Configure OWAS URL via EMS,
Set-OrganizationConfig –WACDiscoveryEndpoint https://mail.domain.com/hosting/discovery
2. WAC stands for Web Access Components.
Check App Log the 140 and 142 Event IDs for MSExchange OWA.
142 means the discovery of the OWAS was successful, 141 means something went wrong.
3. Enable OWAS.
By default, OWA Virtual Directory is already enable WAC Viewing on both public and private computer.
Please run "Get-OwaVirtualDirectory | FL *wac* "to check whether both “WacViewingOnPublicComputersEnabled” and “WacViewingOnPrivateComputersEnabled” parameter is True.
4. Method to collect logs on OWAS.
Run following command in OWAS powershell prompt:
Get-OfficeWebAppsFarm | FL *log*
More details to refer:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-2013-office-web-apps-server-integration.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange Office Web Apps Preview Does not work in OWA. An error occurred while the document preview was being created

Hi,
I have managed to configure intergration between Office Web App server 2013 and Exchange 2013 OWA.
I have created a test users Test1 and Test 2. I have given full access on Test2 mailbox to user test 1.
When I login to owa for user test1 and preview the attachment it works fine.
However when I use "Open another mailbox" in OWA and open test2 mailbox and try to preview the attachments in test2 inbox it errors as
" An error occurred while the document preview was being created. Please try again later " as follows
I am new to office web apps server 2013 and implemented it first time. Can anyone suggest resolutions or troubleshooting ?

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Does the error appear when you directly access test 2 mailbox through OWA?
2. Check if there is 141 error in your event log.
3. Check whether Office web app server connects with Exchange server when the issue happens.
Access the URL: https://hostname/hosting/discovery
4. Grant full access permission again and check the result.
For more information about Office web app integration with Exchange, please refer to the following article:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-2013-office-web-apps-server-integration.html
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

PowerPoint Office Web App Embed Code to start presentation on specific slide

I have SharePoint and Office Web Apps configured and playing nicely. When I go to embed a Powerpoint presentation in my page, it works properly.
However, I'd like to be able to control what slide the presentation opens on by the embed URL. I've tried bashing the embed code options to no avail.
Is there a querystring parameter I can add to the source URL that will automatically start the presentation on a different slide than the first one?

No updates? Seems like it should be possible with a querystring paramter but that's just a logical guess. Anyone know if that is in fact the case and what the parameter to pass would be?

SharePoint 2013 Anonymous (public) site and Office Web Apps Server 2013 issue with download.aspx

Our organization has a public facing anonymous site in SharePoint 2013 which allows access to documents (docx) in a library. ViewFormsLockdown is activated as we present the documents via CQWP / custom template. We are combating the usual
issue of multiple login prompts when using Internet Explorer when a user accesses said document. We also have tried using the Word Viewer (view only mode) from Office Web Apps Server 2013 which works well, but ...
the problem stems from the fact that users can go the file menu from the word view and choose to download the document (which is what we want), unfortunately it looks like the link redirects via /_layouts/15/download.aspx which also presents a login
prompt. Much has been written out there about doing direct links for documents via /_layouts/download.aspx to address multiple login prompts when the document is opening in word (from IE).
I've tried nearly every combination of recommendations (disabling client integration, browser file handling (permissive/strict), ViewFormsLockdown feature, web.config modifications with options and propfind verbs and more) all to varying levels of success,
but never totally getting rid of the prompt. It has been stated that because the downloads.aspx inherits from Microsoft.SharePoint.ApplicationPages.Download this will not allow anonymous access. We really want to use the word view from the Office
web app and have the file download functionality work from the menu there ... can anyone suggest an alternate fix? I might be wishing but will appreciate any guidance offered ...
cheers,
Dean
some reference links (but not all) for various things we've tried:
http://mohitvash.wordpress.com/2013/06/18/sharepoint-download-a-file-programatically/
http://blog.sharedove.com/adisjugo/index.php/2012/09/29/open-sharepoint-files-in-edit-mode-from-client-applications-and-not-read-only/
http://stackoverflow.com/questions/375390/office-documents-prompt-for-login-in-anonymous-sharepoint-site
http://yalla.itgroove.net/tag/anonymous-access/
Glifnard

I'm glad to here that the problem has been fixed. Thank you for sharing your experience here, it will be helpful to other community members who have similar questions.
Cheers,
Steve Fan
TechNet Community Support

Office Web Apps Load Balancing Configuration Issue for SharePoint 2013

I have load balanced servers dedicated for Office Web Apps with name “md1xxxwfe1” and “md1xxxwfe2”
, both this servers are load balanced by CISCO Load balancer. And I have mapped Load Balancer Virutal IP with host name officeapps.jda.corp.local in the DNS records.
Things are working fine if I add new farm by using New-OfficeWebAppsFarm
with server name as internalurl in PowerShell console
as like “ -internalurl http://
md1xxxwfe1 but when I use –internalurl officeapps.jda.corp.local it is not working at all. I’m not getting what to do at this point.
I have gone through following blogs but no luck.
http://blogs.technet.com/b/meamcs/archive/2013/03/27/office-web-apps-2013-multi-servers-nlb-installation-and-deployment-for-sharepoint-2013-step-by-step-guide.aspx
http://blogs.technet.com/b/office_resource_kit/archive/2012/09/11/introducing-office-web-apps-server.aspx
http://davidlimsharepoint.blogspot.in/2013/02/installing-and-configuring-office-web.html
http://sps2013.blogspot.in/2013/09/office-web-apps-with-sharepoint-2013.html
The output of the wfe1 server is attached with this. When I open http:// /hosting/discovery in wfe1 I’m getting following result (attached
screenshot) but it should show hostname rather than server name.
Please help me
Thanks, Ram Ch

Hi Ram ,
For troubleshooting your issue, please take steps as below:
Just about any load balancing solution will work, including a server that runs the Web Server (IIS) role running Application Request Routing (ARR):Install
Application Request Routing
Install the certificate on the load balancer as described under Securing Office Web Apps Server communications by using
HTTPS.
Make sure you have configured the cluster correctly for full internet name:
Reference:
http://technet.microsoft.com/en-us/library/jj219435.aspx#loadbalancer
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 - Office web apps intermittent issue

Similar Messages

Maybe you are looking for