Office Web Apps Integration in a Test Environment

I am trying to test Office Web Apps in an Exchange 2013 test environment and therefore have setup my farm for HTTP only. I have set the WAC Discovery End Point on the Exchange server and I can browse to the XML successfully however when I preview files
they are still being displayed using Web-Ready Document Viewer. I have checked the Event Log and found event ids 140 and 141.
Event 141 lists the following error - There was a failure connecting to or otherwise retrieving Data from the Wac Discovery Service. We will fall back to stellent. Successfully retrieved configuration data from http://server01/hosting/discovery, but
retrieved discovery xml does not contain an external https net zone node.
Do I need to configure HTTPS with a certificate in order to get this working in a test environment or should it work with HTTP?
Thanks

Hi Luke,
Based on my research, I found some people solved this issue via resarting MBX server and CAS server on Exchange 2013 server.
Similar thread for your reference:
Exchange 2013 and Office Web Apps Server Integration
http://social.technet.microsoft.com/Forums/en-US/927a84db-cf54-4546-8b94-374c64eaac2d/exchange-2013-and-office-web-apps-server-integration?forum=exchangesvrgeneral
Please also double check whether there is anything missing during the integration. Offical articles for your reference:
Deploy Office Web Apps Server
http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx
Office Web Apps Server Integration
http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

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

Office Web Apps Integration

Hello,
We are looking to deploy Office Web Apps to integrate with Exchange and share files but I do have a few questions before I deploy this technology.
With this server installed on premise, will this give the users the ability to access the Web Apps Server and upload single files to the office web app server for the purpose of generating a link to this file (lets say Excel for example) and then share this
link to other users so they may co-author the file?
Or does Office Web App strictly only integrate with SharePoint/Exchange/Lync? In our case, we only have Exchange/Lync no SP.
My goal is to give users the ability to co-author documents without going to 3rd party solutions such as Google Docs, etc.
Thanks.

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Best Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

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

Office Web Apps - working in other browsers but not Internet Explorer

Hi there,
I have office web apps on my SharePoint 2013 environment. The previews work file when hovering next to a document but if I try to open it, I get "Sorry, we ran into a problem". It looks as though Excel files open okay but I
have tested Word and Powerpoint documents and I get this error. Also, it only appears to happen in Internet Explorer - Google Chrome and Firefox are okay. Any ideas?

Thanks for the advice. I installed the hoftix (on the OWA server) and now it appears to really be broken - nothing is opening using office web apps anymore.
I found this blog with the same errors I am getting - I'm guessing I will need to uninstall etc. too??
http://blogs.technet.com/b/dodeitte/archive/2013/03/29/issue-with-automatic-updates-enabled-amp-office-web-apps-server-2013-update.aspx

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

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 without excel

Hi,
If office web app is installed in my environment but I do not have excel calculation service running then can I open and edit excel files ?

Office Web Apps 2010 supports Excel files via Excel Web Access (EWA). It only supports the XLSX file type, though (that is Office 2007 and newer). It does not support XLS, like Excel Calc Services does.
Trevor Seward
Follow or contact me at...
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 Server 2013 / Real-Time co-authoring

Hello,
In general, I would like
to ask the development team or product
manager SharePoint /Office web Apps.
As you already know in the cloud
product version introduces new features. Such as
authoring and other unlike on-premises version . This link demonstrate it.
http://blogs.office.com/2013/11/06/collaboration-just-got-easier-real-time-co-authoring-now-available-in-office-web-apps/ .
Please tell me the plans or roadmaps for the implementation
of these functions in the server version. Or Microsoft
has no plans to develop this area?

great, and as i said, we are working to keep parity, but there are still many features which are technically considered in preview in the O365 environment. after several months, depending on stability, feedback, and whether the feature fits well with
the product, it may either be tested to go into on-prem farms and come out of preview or be dropped altogether (auto-hosted apps).
This feature is definitely one that is key to the future of the product, but there isn't a timeline on when it will come to onprem. there ia a lot of additional testing before anything can be integrated to on-prem as the environments have many
more variables than the rather rigid architecture at O365, as well as the fact that the o365 farms have many of the preview features and so then anything to go into a feature for on-prem needs to be re-vetted in farms without those extras and checked for dependencies
(not normally an issue, but still part of the process).
Christopher Webb | Microsoft Certified Master: SharePoint 2010 | Microsoft Certified Solutions Master: SharePoint Charter | Microsoft Certified Trainer| http://tealsk12.org Volunteer Teacher | http://christophermichaelwebb.com

Cannot preview attachments using Office Web App Server 2013 ( Preview )

Got a lab environment to test Office Web App Server integration with Exchange 2013
i have followed the instructions given here
http://technet.microsoft.com/en-US/jj219455
http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a
After all required configuration , i am still unable to preview the office documents from OWA
Receiving the following messages by clicking on the Preview link next to the attachment:
Word Document : "Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word."
Excel Document: "We couldn't find the file you wanted. It's possible the file was renamed, moved or deleted"
PowerPoint: "Sorry, we ran into a problem. Please try again"
As suggested i even see the Application Log the 140 and 142 Event IDs for MSExchange OWA
Already configured to enable the rendering of attachments through OWAS both on public and private computers:
This is what I can see in the ULS log on the Web App Server
WAC Server HttpModule: Beginning request at target [/p/PowerPointFrame.aspx?PowerPointView=SlideShowView&ui=en-US&rs=en-US&WOPISrc=https%3a%2f%2f<Server>%3a443%2fowa%2fuser02%2540<Domain>%2fwopi%2ffiles%2f%40%2fowaatt%3fowaatt%3dLFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%252bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%253d&]
in session [b373a48e-9fca-445b-a7b2-2966f11b18de]
b373a48e-9fca-445b-a7b2-2966f11b18de
UserSessionId=b373a48e-9fca-445b-a7b2-2966f11b18de
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI CheckFileInfo: Start [url:https://<Server>:443/owa/user02%40<Domain>/wopi/files/@/owaatt?owaatt=LFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%2bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%3d]
b373a48e-9fca-445b-a7b2-2966f11b18de
URL generated for WOPI CheckFile Request: https://<Server>:443/owa/user02%40<Domain>/wopi/files/@/owaatt?owaatt=LFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%2bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%3d&access_token=REDACTED_1086&access_token_ttl=0
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI Proof Data: AccessToken Hash '669582051' [1086 bytes], URL 'HTTPS://<Server>/OWA/USER02%40<Domain>/WOPI/FILES/@/OWAATT?OWAATT=LFMTMS01LTIXLTIWODU5NZU2NJITMTE4ODQ1NZE5NY04MDY2NJG5MC0XMTI5VUTGXJ%2BT0AGBAQEAQE1JDE5TSELQZJBHWWTXUTFTZI8YQ3HTSGZXS3IZB1GWZGVFWVHJDKLHBGWWC3F0DNJIQJBZZ0D2EXBDVCTAEEU%3D&ACCESS_TOKEN=REDACTED_1086&ACCESS_TOKEN_TTL=0'
[1354 bytes], TimeStamp '635169449614353585' [8 bytes]
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI Proof: Using Current private key (to sign) that matches Current public key BgIAAACkAABSU0ExAAgAAAEAAQDhPcfARgzhUlTFzo1jhCPHeoylNWp6pBbq6QM6CVQkbFyp4/I+mDzK4JA+AA3BFWLtpQEB7zIEbdjzhdsuYWYAJWBfvfX/3m2E3WRNhcPV8I2rA2T6qWj5Fb6eMNnoz4n2/1sqUXfyIA8mADXUebe9JNyJ+icPluUX+vTNm4m2IWbEgWmJNkgi9OUAq2hmd2lJifbJW8jNr1qzqBCE3ITFwr0L2svMrxfe5nKXVHbZa0EBYxMwHoc3ZkE0dZ0NPle9pq3MObg2+D5RN/w/B0axTJD7G/fQDpZbdsfvKA8mlyCn/vbNpooq5LgvGowTAWmG/tr1kWetfjePAbjBkIK5
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI Proof - Successfully signed the data with the Current private key [4 ms]
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI Proof Keys - WS Farm State has no Old key (this is expected if recently installed)
b373a48e-9fca-445b-a7b2-2966f11b18de
Cannot create WOPI Proof Token - could not find valid Old proof key data
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync (WOPICheckFile,WACSERVER) Starting [mode: GET, url: https://<Server>:443/owa/user02%40<Domain>/wopi/files/@/owaatt?owaatt=LFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%2bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%3d&access_token=REDACTED_1086&access_token_ttl=0]
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync (WOPICheckFile,WACSERVER) End Called
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync::GetResponseCallback - ContentLength:9327
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync::FProcessReadReturn - cbRead:9327
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync::FProcessReadReturn - cbRead:0
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync (WOPICheckFile,WACSERVER) Setting Completion [Time in ms: 3, Bytes Read: 9327 ContentLength: 9327]
b373a48e-9fca-445b-a7b2-2966f11b18de
HttpRequestAsync (WOPICheckFile,WACSERVER) SetCompletion Track start | setting trackers | WebRequest.Create() | Create() returned | setting request headers | setting user agent | setting keep alive | setting timeout callback | Start calling StartResponseProcessing
| StartResponseProcessing._req.BeginGetResponse() | BeginGetResponse() returned | StartResponseProcessing RETURNS | Start RETURNS | End.AsyncWaitHandle.WaitOne() | GetResponseCallback isSync:False | _req.EndGetResponse() | EndGetResponse() returned | RecordResponse
OK | _response.GetResponseStream() | _response.GetResponseStream() RETURNED | DoReadLoopFinished | _getStream.BeginRead() | ReadCallback.sync returning | BeginRead() -> sync:True | DoReadLoopFinished.FProcessReadReturn() | FProcessReadReturn._getStream.EndRead()
| EndR... b373a48e-9fca-445b-a7b2-2966f11b18de
...ead() -> 9327 | FProcessReadReturn._responseStream.Write() | FProcessReadReturn RETURNS True | FProcessReadReturn() -> true | _getStream.BeginRead() | ReadCallback.sync returning | BeginRead() -> sync:True | DoReadLoopFinished.FProcessReadReturn()
| FProcessReadReturn._getStream.EndRead() | EndRead() -> 0 | FProcessReadReturn._responseStream.Write() | FProcessReadReturn RETURNS False | FProcessReadReturn() -> false | DoReadLoopFinished RETURNS true | GetResponseCallback DoReadLoopFinished ->
TRUE | SetCompletion False | b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI Http Request Completed [host machine name:, version:, host correlation:]
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI: Could not deserialize file metadata [url:https://<Server>:443/owa/user02%40<Domain>/wopi/files/@/owaatt?owaatt=LFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%2bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%3d,
e:There was an error deserializing the object of type Microsoft.Office.OpenWebApplication.WopiCheckFileResponse. Encountered unexpected character '<'.]
b373a48e-9fca-445b-a7b2-2966f11b18de
WOPI: Invalid file metadata [url:https://<Server>:443/owa/user02%40<Domain>/wopi/files/@/owaatt?owaatt=LFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%2bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%3d,
triggers:(No Version No FileName No OwnerId), data:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <meta http-equiv="X-UA-Compatible" content="IE=10"
/> <link rel="shortcut icon" href="/owa/auth/15.0.775/themes/resources/favicon.ico" type="image/x-icon"> <meta ...
b373a48e-9fca-445b-a7b2-2966f11b18de
...http-equiv="Content-Type" content="text/html; CHARSET=utf-8"> <meta name="Robots" content="NOINDEX, NOFOLLOW"> <title>Outlook Web App</title> <link type="text/css"
rel="stylesheet" href="/owa/auth/15.0.775/themes/resources/logon.css"> <script type="text/javascript" src="/owa/auth/15.0.775/scripts/premium/flogon.js"></script> <script type="text/javascript"
src="/owa/auth/15.0.775/scripts/premium/flayout.js"></script> <script type="text/javascript">  </script>
<script> var mainLogonDiv = window.document.getElementById("mainLogonDiv"); var layout = DetermineLayout(); var
showPlaceholderText = false; var mainLogonDivClassName; if (layout == LayoutTypeEnum.Mouse) { mainLogonDivClassName = "mouse";
} else if (layout == LayoutTypeEnum.TouchNarrow) { mainLogonDivClassName = "tnarrow"; showPlaceholderText
= true; ...
b373a48e-9fca-445b-a7b2-2966f11b18de
... // Output meta tag for viewport scaling document.write('<meta name="viewport" content="width = 320, initial-scale = 1.0, user-scalable = no" />'); }
else { mainLogonDivClassName = "twide"; showPlaceholderText = true; }
function setPlaceholderText() { window.document.getElementById("username").placeholder = "domain\\user name";
window.document.getElementById("password").placeholder = "password"; window.document.getElementById("passwordText").placeholder = "password";
} function showPasswordClick() { var showPassword = window.document.getElementById("showPasswordCheck").checked;
window.document.getElementById("password"...
b373a48e-9fca-445b-a7b2-2966f11b18de
...).type = showPassword ? "input" : "password"; } </script> </head> <body class="signInBg" style="background: #f2f2f2 url('/owa/auth/15.0.775/themes/resources/bg_gradient_login.png')
repeat-x"/> <noscript> <div id="dvErr"> <table cellpadding="0" cellspacing="0"> <tr> <td><img src="/owa/auth/15.0.775/themes/base/warn.png"
alt=""></td> <td style="width:100%">To use Outlook Web App, browser settings must allow scripts to run. For information about how to allow scripts, consult the Help for your browser. If your browser doesn't
support scripts, you can download <a href="http://www.microsoft.com/windows/ie/downloads/default.mspx">Windows Internet Explorer</a> for access to Outlook Web App.</td> </tr> </table>
</div> </noscript> <form action...
b373a48e-9fca-445b-a7b2-2966f11b18de
...="/owa/auth.owa" method="POST" name="logonForm" ENCTYPE="application/x-www-form-urlencoded" autocomplete="off"> <input type="hidden" name="destination" value="https://<Server>/owa/user02@<Domain>/wopi/files/@/owaatt?owaatt=LFMtMS01LTIxLTIwODU5NzU2NjItMTE4ODQ1NzE5Ny04MDY2Njg5MC0xMTI5VUtGxj%2bT0AgBAQEAQE1jdE5tSElqZjBHWWtXUTFtZi8yQ3htSGZxS3Izb1gwZGVFWVhjdklhbGwwc3F0dnJiQjBzZ0d2eXBDVCtaeEU%3d&access_token=REDACTED_1086&access_token_ttl=0">
<input type="hidden" name="flags" value="4"> <input type="hidden" name="forcedownlevel" value="0">  <div id="mainLogonDiv" class="mouse"> <script> var mainLogonDiv = window.document.getElementById("mainLogonDiv");
... b373a48e-9fca-445b-a7b2-2966f11b18de
... mainLogonDiv.className = mainLogonDivClassName; </script> <div class="sidebar"> <div class="owaLogoContainer">
<img src="/owa/auth/15.0.775/themes/resources/olk_logo_white.png" class="owaLogo" aria-hidden="true" /> <img src="/owa/auth/15.0.775/themes/resources/olk_logo_white_small.png"
class="owaLogoSmall" aria-hidden="true" /> </div> </div> <div class="logonContainer"> <div id="lgnDiv" class="logonDiv"
onKeyPress="return checkSubmit(event)"> <div class="signInImageHeader" role="heading" aria-label="Outlook Web App ">
<img class="mouseHeader" src="/owa/auth/15.0.775/themes/resources/owa_text_blue.png" alt="Outlook Web App " /> </div>
<div class="signInInp...
b373a48e-9fca-445b-a7b2-2966f11b18de
...utLabel" id="userNameLabel" aria-hidden="true">Domain\user name:</div> <div><input id="username" name="username" class="signInInputText" role="textbox" aria-labelledby="userNameLabel"/></div>
<div class="signInInputLabel" id="passwordLabel" aria-hidden="true">Password:</div> <div><input id="password" onfocus="g_fFcs=0" name="password" value=""
type="password" class="signInInputText" aria-labelledby="passwordLabel"/></div> <div class="showPasswordCheck signInCheckBoxText">
<input type="checkbox" id="showPasswordCheck" class="chk" onclick="showPasswordClick()" /> <span>Show password</span>
</div> <div class="signInError" role="alert" tabIndex="0"> </div> <div id="expltxt"
class="signInExpl" role="alert"> ...
b373a48e-9fca-445b-a7b2-2966f11b18de
... </div> <div class="signInEnter"> <div onclick="clkLgn()" class="signinbutton" role="button" tabIndex="0" >
<img class="imgLnk"
src="/owa/auth/15.0.775/themes/resources/Sign_in_arrow.png" alt=""><span class="signinTxt">sign
in</span> </div> <input name="isUtf8" value="1" type="hidden"/> </div>
<div class="hidden-submit"><input type="submit" tabindex="-1"/></div> </div> </div> <div id="cookieMsg" class="logonDiv"
style="display:none"> <div class="signInHeader">Outlook Web App </div> <div class="signInExpl">Please enable cookies for this Web site.<br><br>Cookies are
currently disabled by your browser. Outlook Web...
b373a48e-9fca-445b-a7b2-2966f11b18de
... App requires that cookies be enabled. <br><br>For information about how to enable cookies, see the Help for your Web browser.<br><br><br></div> <div class="signInEnter" >
<div onclick="clkRtry()" style="cursor:pointer;display:inline"> <img class="imgLnk" src="/owa/auth/15.0.775/themes/resources/Sign_in_arrow.png"
alt=""><span class="signinTxt" tabIndex="0">retry</span> </div> </div> </div> </div> </form>
<script> if (showPlaceholderText) { setPlaceholderText(); } </script> </body> </html> ]
b373a48e-9fca-445b-a7b2-2966f11b18de
FileUnknownException loading powerpointframe: Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI Check File at Microsoft.Office.Web.Apps.Common.WopiDocument.CheckWopiFile() at Microsoft.Office.Web.Common.BaseDocumentCache.CheckBaseDocumentInternal(BaseDocument
baseDoc, BaseUser user, Boolean requiresVersion, String canary, Boolean checkCanary, Boolean fUseCacheLookup) at Microsoft.Office.Server.Powerpoint.Web.UI.PptWebControl.CheckFileInfo()
b373a48e-9fca-445b-a7b2-2966f11b18de
ViewOpenEarlyHelper: no presentation Id, failing.
b373a48e-9fca-445b-a7b2-2966f11b18de
IsAuthenticated: False, IsAnonymous: False, AuthType:
b373a48e-9fca-445b-a7b2-2966f11b18de
Secure connection detected, redirecting service endpoint from ppt/view.svc/jsonAnonymous to ppt/view.https.svc/jsonAnonymous
b373a48e-9fca-445b-a7b2-2966f11b18de
WACServer HttpModule: EndRequest Called b373a48e-9fca-445b-a7b2-2966f11b18de
Any suggestions ...

Hi,
Here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/ded515c8-cc0f-4ad4-bed6-e56a0636be79/exchange-office-web-apps-preview-does-not-work-in-owa-web?forum=exchangesvrclients
Hope it hleps you!
Thanks.
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.

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

Office Web Apps Server Default language.

we are using Office Web Apps Server 2013 SP1 with SharePoint 2013 SP1. All servers use English UK regional settings, all SharePoint Sites use English UK as default regional setting.
When we create a new document using Word Web App, the default proofing language defaults to En-US.
How can i configure the office web apps or SharePoint to use English-UK as default.
talwar

Hi talwar,
As I tested in my environment, I couldn’t set default proofing language in Office Web App. And I found a similar case:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/03a6ed63-50d0-48c0-a0d2-89ed36b117b0/set-default-proofing-language-for-office-web-apps-2013?forum=sharepointadmin
Regards,
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] .
Rebecca Tu
TechNet Community Support

SharePoint 2013 SP1 and Office Web Apps SP1 not working using HTTP

Hi I had problems installing and configuring Office Web Apps 2013 SP1 integrated with SP 2013 SP1.
Do you know if there is any issue?
This is the error in the owa side:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/24/2014 10:04:54 PM
Event time (UTC): 4/24/2014 9:04:54 PM
Event ID: 86c0893b9e89427babde2c4e931e0a28
Event sequence: 17
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/wv-1-130428459380785645
Trust level: Full
Application Virtual Path: /wv
Application Path: C:\Program Files\Microsoft Office Web Apps\WebWordViewer\
Machine name: SPS-OWAS01
Process information:
Process ID: 13696
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpUnhandledException
Exception message: Exception of type 'System.Web.HttpUnhandledException' was thrown.
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlersPossiblyUnderLock(Boolean onPageThread)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlers(Boolean onPageThread)
Unable to determine zone from request
at Microsoft.Office.OpenWebApplication.WopiOM.DecomposeWopiUrl(List`1 actionList, HttpRequest request, WopiAction currentAction, String extension, Boolean forceSsl)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSUrlAdapter.ChangeActionInWacUrl(HttpRequest request, WacUrlApplication application, WacUrlAction currentAction, WacUrlAction targetAction)
at Microsoft.Office.Web.WordViewer.Controls.Application.RegisterApplicationInit()
at Microsoft.Office.Web.Common.AApplication.OnPreRender(EventArgs e)
at Microsoft.Office.Web.WordViewer.Controls.Application.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
at System.Web.UI.Page.Render(HtmlTextWriter writer)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL:
http://sps-owas01/wv/wordviewerframe.aspx?ui=en-US&rs=en-US&WOPISrc=http://sharepoint.internal/_vti_bin/wopi.ashx/files/8b568ecdf89c44d8afd4132bc0b82b32&sc=http://sharepoint.internal/SitePages/Home.aspx&wdEnableRoaming=1
Request path: /wv/wordviewerframe.aspx
User host address: 10.10.199.27
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 7
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlersPossiblyUnderLock(Boolean onPageThread)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlers(Boolean onPageThread)
Custom event details:
José Quinto Zamora SharePoint and Search Specialist MCITP and MCPD in SharePoint 2010
http://joSharePoint.com

It show me also this message:
<meta content="width=device-width" name="viewport" /><style></style>
Server Error in '/wv' Application.
Unable to determine zone from request
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Office.OpenWebApplication.DiscoveryEntryNotFoundException: Unable to determine zone from request
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[DiscoveryEntryNotFoundException: Unable to determine zone from request]
Microsoft.Office.OpenWebApplication.WopiOM.DecomposeWopiUrl(List`1 actionList, HttpRequest request, WopiAction currentAction, String extension, Boolean forceSsl) +598
Microsoft.Office.Web.Apps.Environment.WacServer.WSUrlAdapter.ChangeActionInWacUrl(HttpRequest request, WacUrlApplication application, WacUrlAction currentAction, WacUrlAction targetAction) +161
Microsoft.Office.Web.WordViewer.Controls.Application.RegisterApplicationInit() +1766
Microsoft.Office.Web.Common.AApplication.OnPreRender(EventArgs e) +1531
Microsoft.Office.Web.WordViewer.Controls.Application.OnPreRender(EventArgs e) +17
System.Web.UI.Control.PreRenderRecursiveInternal() +113
System.Web.UI.Control.AddedControl(Control control, Int32 index) +12375740
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +150
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +246
System.Web.UI.Page.Render(HtmlTextWriter writer) +40
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +150
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5363
José Quinto Zamora SharePoint and Search Specialist MCITP and MCPD in SharePoint 2010
http://joSharePoint.com

Office Web Apps - Best Practice for App Pool Security Account?

Guys,
I am finalising my testing of Office Web Apps, and ready to move onto deploying it to my live farm.
Generally speaking, I put service applications in their own application pool.
Obviously by doing so this has an overhead on memory and processing, however generally speaking it is best practice from a security perspective when using separate accounts.
I have to create 3 new service applications in order to deploy Office Web Apps, in my test environment these are using the Default SharePoint app pool.
Should I create one application pool for all my office web apps with a fresh service account, or does it make no odds from a security perspective to run them in the default app pool?
Cheers,
Conrad
Conrad Goodman MCITP SA / MCTS: WSS3.0 + MOSS2007

i run my OWA under it's own service account (spOWA) and use only one app pool. Just remember that if you go this route, "When
you create a new application pool, you can specify a security account used by the application pool to be either a predefined Network Service account or a managed account. The account must have db_datareader, db_datawriter, and execute permissions for the content
databases and the SharePoint configuration database, and be assigned to the db_owner role for the content databases." (http://technet.microsoft.com/en-us/library/ff431687.aspx)

Office Web Apps - Office Web Apps was unable to find the specified certificate

Hello,
Let me start by saying I did not see a forum listed for Office Web Apps and figured the SharePoint forum would be the second best place to post this. With that said, here's my issue...
I installed OWA 2013 on a Windows Server 2012 (not R2) VM and installed all the prereqs as described here: http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx Since this is a test environment, I'm planning on using a self-signed
cert which appears to be supported based on info found here: http://technet.microsoft.com/en-us/library/2e147f11-6f47-46bc-90bf-b2f179958d11(v=office.15)#certificate.
I created the cert using the following command:
New-SelfSignedCertificate -DnsName owa.test.local -CertStoreLocation cert:\LocalMachine\My
I then edited the cert's properties in the Cert Manager MMC snap-in and added a friendly name of "2014_OWA_Cert". I then proceeded to try and create the OWA farm by running:
New-OfficeWebAppsFarm -InternalUrl "https://owa.test.local" -CertificateName "2014_OWA_Cert" -EditingEnabled
This produces the following error:
New-OfficeWebAppsFarm : Office Web Apps was unable to find the specified certificate.
At line:1 char:1
+ New-OfficeWebAppsFarm -InternalUrl "https://owa.test.local" -CertificateNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [New-OfficeWebAppsFarm], ArgumentException
+ FullyQualifiedErrorId : CertificateNotFound,Microsoft.Office.Web.Apps.Administration.NewFarmCommand
What gives?

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

Office Web Apps Integration in a Test Environment

Similar Messages

Maybe you are looking for